Document how to consume post-submit / nightly images

[sbueringer]

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:

• Build via: https://prow.k8s.io/?repo=kubernetes-sigs%2Fcluster-api-provider-vsphere&job=post-cluster-api-provider-vsphere-push-images
  • gcr.io/k8s-staging-capi-vsphere/cluster-api-vsphere-controller:main
  • gcr.io/k8s-staging-capi-vsphere/cluster-api-vsphere-controller:v20230802-v1.8.0-beta.1-8-g2fae0a97
  • gcr.io/k8s-staging-capi-vsphere/cluster-api-vsphere-controller:release-1.7
  • gcr.io/k8s-staging-capi-vsphere/cluster-api-vsphere-controller:v20230802-v1.7.1-25-g3ec8d66d
• Build via: https://prow.k8s.io/?job=cluster-api-provider-vsphere-push-images-nightly
  • gcr.io/k8s-staging-capi-vsphere/cluster-api-vsphere-controller:nightly_main_20230802

Manifests:

• Build via: https://prow.k8s.io/?job=cluster-api-provider-vsphere-push-images-nightly
  • Google Cloud UI: https://console.cloud.google.com/storage/browser/artifacts.k8s-staging-capi-vsphere.appspot.com/components/nightly_main_20230802
  • Example for public file URL: https://storage.googleapis.com/artifacts.k8s-staging-capi-vsphere.appspot.com/components/nightly_main_20230802/infrastructure-components.yaml

[sbueringer]

/help

[k8s-ci-robot]

@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](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/2148): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[damdo]

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: https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4968 LMK what you think here. Thanks!

[sbueringer]

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

[damdo]

Awesome, thank you!

[fabriziopandini]

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]

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