-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Umbrella Issue] Migrate prow jobs to community clusters #29722
Comments
/sig k8s-infra |
For kops, we have a separate issue: kubernetes/k8s.io#5127 |
@dims Can I pick up the |
@dims @ameukam I think the Example in #29724 where I WAG'd .5CPU and 2GB and asked the cluster lifecycle leads to review. |
I would like to learn more about this , so I will pick one kubernetes-sigs/kustomize | Search Results | |
@dims hi, thanks for sharing the steps. Also I noticed PR's moving to new clusters with just specifying the new cluster name, there are others specifying resource quotas (CPU/memory) while migrating. Is the latter requirement or generally maybe recommended while just specifying the name is also enough? |
The Google-owned clusters did not require any resource definitions whereas the community-owned clusters do. If a job already has resource quotas (both requests and limits) then just the name is enough. If the job is missing any resource quotas then those will need to be added or else the |
I will be working on kubernetes/node-problem-detector | Prow Results | Search Results |
Part of: - kubernetes#29722 Move a few jobs still running on Google Infra. Signed-off-by: Arnaud Meukam <[email protected]>
Part of: - kubernetes#29722 Move a few jobs still running on Google Infra. Signed-off-by: Arnaud Meukam <[email protected]>
/lifecycle frozen |
xref: #32432 |
We're also keeping this list up to date: https://github.com/kubernetes/test-infra/blob/master/docs/job-migration-todo.md |
filed a few warnings: + messages in slack, in addition to the kubernetes-dev emails |
NPD is actually done now. We're getting really close. We have DO spending info now and sorted out credentials, @upodroid has been migrating those jobs. I migrated the slack infra and some more of the test-infra trusted jobs. kops jobs are being migrated with DO as well. |
secrets-store-csi-driver seems like a new wrinkle https://kubernetes.slack.com/archives/C09QZ4DQB/p1722024643376909 we know that vsphere jobs are blocked on resource availability and may not making it kubernetes/k8s.io#6877 azure jobs are in flight and making steady progress now most other jobs are done, leaving a handful of trusted project automation jobs in #32432 , and some scalability related jobs we may have missed others and should do another pass through these to identify the categories |
#33127 makes it a little more obvious what grouping remaining jobs are in based on the secrets Since filed a couple more tracking issues ... In addition to the vsphere + azure e2e jobs we also have:
|
Closing this in favor of #33226 and #32432 Announcement at https://groups.google.com/a/kubernetes.io/g/dev/c/qzNYpcN5la4 |
In an ongoing effort to migrate to community-owned resources, SIG K8S Infra and SIG Testing are working to complete the migration of jobs from the Google-owned internal GKE cluster to community-owned clusters.
All jobs in the Prow Default Cluster that do not depend on external cloud assets should attempt migrate to
cluster: eks-prow-build-cluster
.What needs to be done?
To get started please see eks-jobs-migration for details.
Fork and check out the kubernetes/test-infra repository, then follow the steps below:
pull-jobset-test-integration-main
from the"Prow Results"
link below.pull-jobset-test-integration-main
is defined in from the"Search Results"
link, in the job definition look for acluster:
key, if there isn't one then the job runs in the default cluster, So add onecluster: eks-prow-build-cluster
. NOTE: if you see any entries underlabel
that saysgce
skip this job and go to the next time as this is not ready to be moved yet.NOTE: The Google-owned clusters did not require any resource definitions whereas the community-owned clusters do. If your merge is failing the
pull-test-infra-unit-test
job, please add CPU/Memory requests/limits. Work with the appropriate sig owners to determine the necessary capacity for each job.Below is a list of repos that currently have jobs in the default cluster.
Repos with default cluster jobs found
k/csi
jobs to community cluster #30330k/csi
jobs to community cluster #30330k/csi
jobs to community cluster #30330k-csi
gen-jobs to enable different clusters to be used #29812kubernetes-sigs/azuredisk-csi-driver | Prow Results | Search Results| Jobs require azure credentialskubernetes-sigs/azurefile-csi-driver | Prow Results | Search Results| Jobs require azure credentialscli-utils
jobs toeks-prow-build-cluster
#29742kubernetes-sigs/cloud-provider-azure | Prow Results | Search Results| Jobs require azure credentialskubernetes-sigs/gcp-compute-persistent-disk-csi-driver | Prow Results | Search Results| Jobs require GCPkubernetes-sigs/gcp-filestore-csi-driver | Prow Results | Search Results| Jobs require GCPibm-powervs-block-csi-driver
toeks-prow-build-cluster
#29843ibm-vpc-block-csi-driver
toeks-prow-build-cluster
#29844kubernetes-sigs/kube-storage-version-migrator | Prow Results | Search Resultsvsphere-csi-driver
toeks-prow-build-cluster
#29849cloud-provider-aws
toeks-prow-build-cluster
#29850cloud-provider-gcp
tok8s-infra-prow-build
#29852cloud-provider-openstack
toeks-prow-build-cluster
#29853cloud-provider-vsphere
toeks-prow-build-cluster
#29854dns
job to community cluster #30384k8s.io
jobs to EKS cluster #30379node-problem-detector
jobs toeks-prow-build-cluster
#29751The text was updated successfully, but these errors were encountered: