Question regarding CAPD infrastructure components manifest

[abhay-krishna]

I downloaded the CAPD manifest linked in the v1.2.0 release and noticed that the image referenced in the Deployment was tagged main.

$ curl -fsSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.2.0/infrastructure-components-development.yaml | grep image:
        image: gcr.io/k8s-staging-cluster-api/capd-manager:main

For previous releases however it is tagged with that tag version

$ curl -fsSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.5/infrastructure-components-development.yaml | grep image:
        image: gcr.io/k8s-staging-cluster-api/capd-manager:v1.1.5

I was wondering if this is intended for every new version that comes out, where the latest CAPD image deployed will be tagged main.

[abhay-krishna]

/area provider/docker

[killianmuldoon]

/assign

Definitely seems like an issue with the latest release.

[killianmuldoon]

@abhay-krishna Thanks for catching this! The image is published and available so you should change the image in your local manifest to gcr.io/k8s-staging-cluster-api/capd-manager:v1.2.0. I'm going to figure out our options for updating the release with the fixed manifest.

[killianmuldoon]

This should be fixed in the current release branch, and I've got a PR out to fix the root cause in how our manifests are being generated. Thanks again for catching this!