Migrate remaining CI jobs to community infra by ~August 1st

[BenTheElder]

As previously announced in february ...

https://groups.google.com/a/kubernetes.io/g/dev/c/p6PAML90ZOU

This repo is at risk with a handful of jobs still not migrated.

I would've filed something sooner but I thought they were all from the Azure jobset (a few other similar projects are ...) which are being bulk migrated now that we have SIG K8s Infra Azure resources.

There are a few CI jobs for this repo that use GCP, and don't appear to be able to just use our commodity GCP Kubernetes e2e test project rental.

thread: https://kubernetes.slack.com/archives/C09QZ4DQB/p1722024643376909

#sig-k8s-infra can help ... but it's not clear what exactly is needed in order to provide comparable resources under the community infrastructure.

Currently these jobs are at risk of being shut down, though they could be recreated later.

/kind bug

[aramase]

/assign @dargudear-google

[k8s-ci-robot]

@aramase: GitHub didn't allow me to assign the following users: dargudear-google.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @dargudear-google

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.

[BenTheElder]

You can find the jobs by searching "secrets-store" in https://github.com/kubernetes/test-infra/blob/master/docs/job-migration-todo.md

[BenTheElder]

Secrets	File Path	Job	Link
[]	config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-config.yaml	pull-secrets-store-csi-driver-e2e-akeyless	Search Results
[]	config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-config.yaml	pull-secrets-store-csi-driver-e2e-gcp	Search Results
[]	config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-config.yaml	release-secrets-store-csi-driver-e2e-gcp	Search Results
[]	config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-config.yaml	secrets-store-csi-driver-e2e-gcp-postsubmit	Search Results

[BenTheElder]

kubernetes/test-infra#33226

removing these will block kubernetes/test-infra#33129 which will block migrating prow

we can re-create these on community resources once someone explains what GCP resources are necessary to provision in SIG k8s Infra

[BenTheElder]

Same issue, but akeyless instead kubernetes/test-infra#33232

Will have to reach out to #sig-k8s-infra slack.k8s.io, or https://github.com/kubernetes/k8s.io/issues to sort out standing up resources on prow.k8s.io going forward. We will not be retaining any dependency on arbitrary company-internal assets in the Kubernetes project's CI. See the announcements linked previously for more details.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dargudear-google]

This is being discussed in kubernetes/k8s.io#7246