-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Push manifests for main & release-.* #10521
🌱 Push manifests for main & release-.* #10521
Conversation
/assign @chrischdi |
Signed-off-by: Stefan Büringer [email protected]
82bae23
to
20d8eea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool!
/lgtm
/approve
/area release
/hold
(just in case)
LGTM label has been added. Git tree hash: 2ae70053e4fa118d0114279d50db8b8e94ed4094
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi, killianmuldoon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel Let's give it a try :D |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
This target is run on main and all release-branches (https://github.com/kubernetes/test-infra/blob/996976242b664e8f55ce6873692b0ebc2da5de02/config/jobs/image-pushing/k8s-staging-cluster-api.yaml#L13).
While we already have images like:
gcr.io/k8s-staging-cluster-api/cluster-api-controller:release-1.7
,gcr.io/k8s-staging-cluster-api/cluster-api-controller:main
available. This PR will give us corresponding manifests.This should make it very easy for folks to consume manifests / images based on the last commit of main and release branches.
Bonus: we'll also get manifests for release tags in the staging bucket.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #