-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
release-blocking jobs must run in dedicated cluster: ci-kubernetes-build #19483
Comments
/sig release |
Current obstacle is deciding how to allow the ci-kubernetes-build-canary job to push to gcr.io/k8s-staging-ci-images. Currently:
What this means:
What could we do for pushing to
|
+1 for doing this for each staging project. |
which is not enough to make the job successful. |
My read of GCS permissions is that members of the group have write and admin privileges to the bucket
|
Per https://cloud.google.com/iam/docs/understanding-roles roles/storage.legacyBucketOwner
roles/storage.legacyBucketWriter
roles/storage.objectAdmin
roles/storage.admin
|
Perhaps the service account isn't getting picked up as a group member
|
Opened kubernetes/k8s.io#1401 to do what I did manually
Which I verified as working via a push which had failed before:
|
Ref : kubernetes#19483 Part of: kubernetes#18549 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref : kubernetes#19483 Part of: kubernetes#18549 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref : kubernetes#19483 Part of: kubernetes#18549 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref : kubernetes#19483 Part of: kubernetes#18549 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Add canary jobs for ci-kubernetes-build job variants.
I need to see what is the status of this item and maybe we can plan the next steps (@LappleApple) @ameukam do you have any updates that you can provide to check where we are with this issue? |
@LappleApple @cpanato The only update I'm aware is the switch to |
IMO next steps are:
|
/milestone v1.21 |
/priority important-longterm |
/remove-priority important-longterm |
Ensure periodic-kubernetes-bazel-build can run k8s-infra-prow-build cluster and push artifacts on k8s-release-dev bucket. Related to : kubernetes#19483 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
|
/close |
@spiffxp: Closing this issue. In response to this:
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/test-infra repository. |
What should be cleaned up or changed:
This is part of #18549
To properly monitor the outcome of this, you should be a member of k8s-infra-prow-viewers@kubernetes.io. PR yourself into https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml#L603-L628 if you're not a member.
NOTE: I am not tagging this as "help wanted" because it is blocked on kubernetes/k8s.io#846. I would also recommend doing ci-kubernetes-build-fast first. Here is my guess at how we could do this:
It will be helpful to note the date/time that PR's merge. This will allow you to compare before/after behavior.
Things to watch for the job
ci-kubernetes-build
for 6hci-kubernetes-build
for 6hThings to watch for the build cluster
Keep this open for at least 24h of weekday PR traffic. If everything continues to look good, then this can be closed.
/wg k8s-infra
/sig testing
/area jobs
The text was updated successfully, but these errors were encountered: