I've asked @idvoretskyi to provide credentials to test-infra
/assign @fejta
please assign to the appropriate person
/assign
/assign @zmerlynn
/unassign @fejta
I set up the current aws creds in prow, if you provide a new one I can swap them out :-)
Thanks Sen!
@spiffxp new AWS accounts created, details DM'ed.
cc @krzyzacy @fejta
from @zmerlynn : It should mostly be a matter of flipping out the secrets, but there's a little setup on the AWS side as well (you need to configure Route53 for DNS)
I guess I'll add a new secret and try out
error reading cluster configuration: error reading cluster configuration "e2e-kops-aws-canary.test-aws.k8s.io": error reading s3://k8s-kops-jenkins/e2e-kops-aws-canary.test-aws.k8s.io/config: Could not retrieve location for AWS bucket k8s-kops-jenkins
of course not that easy
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kops-aws-cncf-canary/59 is the first run actually runs tests, however follow up runs are all busted - need more investigation
https://k8s-testgrid.appspot.com/sig-testing-canaries#kops-aws-cncf-canary is looking better now but still have failure now-and-then
/assign @justinsb
also pull Justin in as he's also helping triaging the job :-)
fyi this is going on for a while, we'll switch account for the rest of the jobs O(Friday), if the presubmit gets flaky upon cluster start we'll move it to non-blocking for a while until people cares :-)
/close
will monitor presubmit job for a while and see if we need to move it to unblocking until the quota change resolves. cc @kubernetes/sig-aws-misc @chrislovecnm @justinsb