Remove non-alpha features from jobs.

[rayandas]

This PR remove non-alpha features from job ci-kubernetes-e2e-gci-gce-alpha-features and pull-kubernetes-e2e-gce-alpha-features.
Partially fixes #23642

Signed-off-by: Rayan Das rayandas91@gmail.com

[k8s-ci-robot]

Hi @rayandas. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rayandas]

/ok-to-test

[k8s-ci-robot]

@rayandas: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rayandas]

cc: @mmiranda96

[spiffxp]

/ok-to-test

[mmiranda96]

Thanks for your work @rayandas ! Let's run these jobs and see the result.
/test pull-kubernetes-e2e-gce-alpha-features
/test ci-kubernetes-e2e-gci-gce-alpha-features

[k8s-ci-robot]

@mmiranda96: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-test-infra-bazel
• /test pull-test-infra-gubernator
• /test pull-test-infra-verify-file-perms
• /test pull-test-infra-yamllint
• /test pull-test-infra-prow-checkconfig
• /test pull-test-infra-integration
• /test pull-test-infra-test-beta

Use /test all to run the following jobs that were automatically triggered:

• pull-test-infra-bazel
• pull-test-infra-gubernator
• pull-test-infra-verify-file-perms
• pull-test-infra-yamllint
• pull-test-infra-prow-checkconfig
• pull-test-infra-integration

In response to this:

Thanks for your work @rayandas ! Let's run these jobs and see the result.
/test pull-kubernetes-e2e-gce-alpha-features
/test ci-kubernetes-e2e-gci-gce-alpha-features

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mmiranda96]

I think I can't trigger the CI job. Triggering just the PR job...
/test pull-kubernetes-e2e-gce-alpha-features

[k8s-ci-robot]

@mmiranda96: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-test-infra-bazel
• /test pull-test-infra-gubernator
• /test pull-test-infra-verify-file-perms
• /test pull-test-infra-yamllint
• /test pull-test-infra-prow-checkconfig
• /test pull-test-infra-integration
• /test pull-test-infra-test-beta

Use /test all to run the following jobs that were automatically triggered:

• pull-test-infra-bazel
• pull-test-infra-gubernator
• pull-test-infra-verify-file-perms
• pull-test-infra-yamllint
• pull-test-infra-prow-checkconfig
• pull-test-infra-integration

In response to this:

I think I can't trigger the CI job. Triggering just the PR job...
/test pull-kubernetes-e2e-gce-alpha-features

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rayandas]

@mmiranda96 I think we cant trigger pull-kubernetes-e2e-gce-alpha-features job also. It has to be one from the bot's message above.

[mmiranda96]

Yeah, I'm not sure why the job doesn't trigger. I'll ask about it on Slack.

[spiffxp]

/approve
/lgtm
FWIW I'm inclined to suggest we just merge this and watch the CI job to see if it breaks. If it does, we can revert and take the more cautious route of duplicating the presubmit as a manually triggered job under a new name like pull-kubernetes-e2e-gce-alpha-features-canary

/hold
Please /hold cancel if you agree with this approach, or update the PR to take the more cautious approach first

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rayandas, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-cloud-provider/OWNERS [spiffxp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mmiranda96]

Considering that this PR only makes the test set smaller, I see very low risk.
/lgtm
/hold cancel

Thanks everyone!

[k8s-ci-robot]

@rayandas: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key gcp-gce.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml

In response to this:

This PR remove non-alpha features from job ci-kubernetes-e2e-gci-gce-alpha-features and pull-kubernetes-e2e-gce-alpha-features.
Partially fixes #23642

Signed-off-by: Rayan Das rayandas91@gmail.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.