Image tag 1.30.3 in container registry registry.k8s.io/autoscaling/cluster-autoscaler with no associated release

[wcarlsen]

Which component are you using?:

Cluster-autoscaler and it's associated helm chart.

What version of the component are you using?:

Component version:

• Helm chart version: 9.43.0
• Cluster-autoscaler version: 1.30.2

What k8s version are you using (kubectl version)?:

kubectl version Output

$ kubectl version
Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.30.4-eks-a737599

What environment is this in?:

AWS EKS

What did you expect to happen?:

I see an image tag 1.30.3 in container registry registry.k8s.io/autoscaling/cluster-autoscaler with no associated release.

What happened instead?:

I expected a tag 1.30.3 with no associated release to not be present in the registry. Maybe this comes from a deleted release?

How to reproduce it (as minimally and precisely as possible):

docker pull registry.k8s.io/autoscaling/cluster-autoscaler:v1.30.3

Anything else we need to know?:

[adrianmoisey]

/area cluster-autoscaler

[Shubham82]

@wcarlsen, I think it is due to Promotion PR (kubernetes/k8s.io#7429) for images of the CA Patch release being merged and the corresponding CA Patch release not yet released (#7315)

[Shubham82]

cc @gjtempleton, please correct me if I missed something here.
PTAL!

[gjtempleton]

Yep, that's on me. Apologies, got to the point of promoting the images but not the tags and associated release notes before some issues. Will get this resolved today.

[gjtempleton]

/assign @gjtempleton

[Shubham82]

Yep, that's on me. Apologies, got to the point of promoting the images but not the tags and associated release notes before some issues. Will get this resolved today.

Thanks @gjtempleton

[gjtempleton]

Release notes and associated tags now cut, apologies for the delay @wcarlsen

[Shubham82]

Release notes and associated tags now cut, apologies for the delay @wcarlsen

Thanks, @gjtempleton for all the work.

[Shubham82]

Hi @wcarlsen, can we close this issue, as it is resolved?

[wcarlsen]

Yes off course. Thanks for the reminder @Shubham82 and no worries @gjtempleton.