-
Notifications
You must be signed in to change notification settings - Fork 296
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
Document how to consume post-submit / nightly images #2148
Comments
/help |
@sbueringer: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
Hey @sbueringer RE: documenting this process, I'm working on this for CAPA and wanted to see if this could be replicated for CAPV in some capacity, so we can somehow align how some of the providers document this. See: kubernetes-sigs/cluster-api-provider-aws#4968 |
Nice, yup roughly the same should work for CAPV so we can document it the same way |
Awesome, thank you! |
I did some work in the past to use CAPI/CAPD nightly builds (see https://cluster-api.sigs.k8s.io/clusterctl/developers.html?highlight=nightl#nightly-builds) |
Interesting. Now that you're referring to clusterctl, I remember this one recent PR: https://github.com/kubernetes-sigs/cluster-api/pull/9797/files |
After the recent changes in #2051 we are now publishing images on every merge to the main and release branches.
Additionally for the main branch we tag images with a nightly tag and publish corresponding manifests (e.g. infrastructure-components.yaml & cluster-templates) to GCS.
Let's document where those images are available / how to consume them (e.g. via clusterctl if that is easily possible (?)).
Images:
Manifests:
The text was updated successfully, but these errors were encountered: