Skip to content
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

Open
sbueringer opened this issue Aug 3, 2023 · 7 comments
Open

Document how to consume post-submit / nightly images #2148

sbueringer opened this issue Aug 3, 2023 · 7 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation.

Comments

@sbueringer
Copy link
Member

sbueringer commented Aug 3, 2023

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:

@sbueringer sbueringer added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 3, 2023
@sbueringer
Copy link
Member Author

/help

@k8s-ci-robot
Copy link
Contributor

@sbueringer:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

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
by commenting with the /remove-help command.

In response to this:

/help

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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 18, 2023
@damdo
Copy link
Member

damdo commented May 14, 2024

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
LMK what you think here.
Thanks!

@sbueringer
Copy link
Member Author

sbueringer commented May 14, 2024

Nice, yup roughly the same should work for CAPV so we can document it the same way

@damdo
Copy link
Member

damdo commented May 14, 2024

Awesome, thank you!

@fabriziopandini
Copy link
Member

Let's document where those images are available / how to consume them (e.g. via clusterctl if that is easily possible (?)).

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)
We could probably build up on this work. Happy to pair if it can help

@sbueringer
Copy link
Member Author

Interesting. Now that you're referring to clusterctl, I remember this one recent PR: https://github.com/kubernetes-sigs/cluster-api/pull/9797/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

No branches or pull requests

4 participants