Finish Migrating To Community CI By August 1st

BenTheElder commented 4 days ago

/kind bug

kOps is one of the few projects with many remaining jobs, please migrate by August 1st or risk losing CI coverage.

ameukam commented 4 days ago

cc @hakman @justinsb @rifelpet

rifelpet commented 13 hours ago

The remaining jobs that havent been migrated can be categorized into:

Periodic jobs that publish version markers to a GCS bucket, currently gs://kops-ci. Example usage (1, 2, 3)

I see a k8s-infra-kops-ci-results bucket was created years ago: https://github.com/kubernetes/k8s.io/pull/2678 but is not mentioned in any prow job nor in kubetest2-kops. Should we use this bucket or is there a more appropriate project we should create a new bucket in? Currently these jobs use a static AWS credential secret and also have write access to the kops-ci GCS bucket. Which prow cluster should we migrate to and how will we acquire both AWS and GCP credentials in one job? We currently acquire random GCP projects from boskos but don't use boskos with AWS.
The presubmit E2E jobs publish artifacts to a k8s-staging-kops GCS bucket, used by the E2E cluster provisioned in the test. Can you confirm gs://k8s-staging-kops is in a community-owned project? Similar to above we need a way to get credentials for its project while also using AWS credentials for cluster provisioning. If it isn't community-owned then we'll need a new bucket.
The e2e-kops-aws-upgrade-k12[456] periodic jobs haven't been migrated because their k/k e2e.test binaries use older aws-sdk-go versions that dont support the authentication methods needed to run in the prow EKS cluster. We can either delete these 1.24 - 1.26 jobs or try to migrate them to EKS and skip any failing tests.
The Digital Ocean jobs are still waiting on having an account available from the CNCF.

cc @upodroid any recommendations you can provide here?

kubernetes / kops