Mahamed Ali
Mahamed Ali
For now, let's retain the existing behaviour as AWS presubmits have been writing to the k8s-staging-kops bucket and let's try to switch to dynamic buckets on AWS. As for gs://k8s-infra-kops-ci-results,...
We do need to ship this to fix the AWS presubmits publishing to the k8s-staging-kops bucket. We carried over that practice when the jobs were migrated to the community cluster.
https://github.com/kubernetes-sigs/prow/blob/main/.ko.yaml +1 for building a unified base image for prow that has git, the kubectl auth plugins for our cloud vendors
We can migrate that job to the community cluster and update the .ko.yaml references
> Hopefully also the ~6 kOps D.O. jobs I added all the creds now
/hold cancel
/cc @alvaroaleman
Closing as prow moved to its own repo