Modify gcp-gce e2e-gci default periodic job

[Rajalakshmi-Girish]

Changing ci-kubernetes-e2e-gci-gce master job to match with release branch job at ci-kubernetes-e2e-gce-cos-k8sbeta-default
Ref: https://kubernetes.slack.com/archives/C2C40FMNF/p1734529922763579?thread_ts=1734528191.048989&cid=C2C40FMNF

• The job name is being changed from ci-kubernetes-e2e-gci-gce to ci-kubernetes-e2e-gce-cos-master-default so as to make this use config-forker in future as per the plan here

• Addition of --env=ENABLE_CACHE_MUTATION_DETECTOR=true helps catch the scenario where anything mutates a shared informer cache as per @dims comment here

• Removing the args --gcp-node-image=gci and --gcp-nodes=4 in master branch job will probably cut down the run to single node cluster. Looks like single node would be enough as release branch jobs are not having these args here and are running fine.

• The timeout value of job and the timeout arg passed to test run are increased as per https://github.com/kubernetes/test-infra/blob/master/releng/test_config.yaml#L332 and https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/generated/generated.yaml#L294

[aojea]

/assign @mauriciopoppe

[mauriciopoppe]

/lgtm

[dims]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, Rajalakshmi-Girish

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 [dims]

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

[k8s-ci-robot]

@Rajalakshmi-Girish: 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:

Changing ci-kubernetes-e2e-gci-gce master job to match with release branch job at ci-kubernetes-e2e-gce-cos-k8sbeta-default
Ref: https://kubernetes.slack.com/archives/C2C40FMNF/p1734529922763579?thread_ts=1734528191.048989&cid=C2C40FMNF

• The job name is being changed from ci-kubernetes-e2e-gci-gce to ci-kubernetes-e2e-gce-cos-master-default so as to make this use config-forker in future as per the plan here

• Addition of --env=ENABLE_CACHE_MUTATION_DETECTOR=true helps catch the scenario where anything mutates a shared informer cache as per @dims comment here

• Removing the args --gcp-node-image=gci and --gcp-nodes=4 in master branch job will probably cut down the run to single node cluster. Looks like single node would be enough as release branch jobs are not having these args here and are running fine.

• The timeout value of job and the timeout arg passed to test run are increased as per https://github.com/kubernetes/test-infra/blob/master/releng/test_config.yaml#L332 and https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/generated/generated.yaml#L294

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-sigs/prow repository.