There are no official published images for CCM

[frezbo]

I see that k8s.gcr.io/cloud-controller-manager is published up to version 1.15.9. Are the images not published anymore or has the images registry changed?

[zetaab]

@jingxu97 @saad-ali @cici37 do you have idea could owners of this repository build the image and start publishing it? We (kOps) are thinking to start implementing external ccm for GCP but it is really difficult if the basics like CI release pipeline is missing.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[zetaab]

/remove-lifecycle stale

[pagottoo]

I folks, we are planning to upgrade our k8s distribution to the latest k8s version, but to support GCE we need to deploy CCM. any position about the release process of this repo? or each one need to clone and DIY? the images will be delivery publicly?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ialidzhikov]

/remove-lifecycle stale

[ialidzhikov]

/assign @jprzychodzen

[ialidzhikov]

/priority important-soon

[ialidzhikov]

ping @jprzychodzen

[katexochen]

@jprzychodzen Any updates on this issue? Seems like there are still no images available.

[jprzychodzen]

/assign @aojea

I guess this has happened, right?

[katexochen]

I guess this has happened, right?

It hasn't. You can check with

curl -sSL registry.k8s.io/v2/cloud-controller-manager/tags/list | jq .tags[]

[aojea]

There is a postsubmit jjobs that publish images after each. merge

https://gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager

Those registry.k8s.io/v2/cloud-controller-manager/tags/list sounds like the released images , I really don't have time for that, but I'm happy to help with reviews

[ialidzhikov]

I am bringing the topic raised in https://github.com/kubernetes/cloud-provider-gcp/issues/300#issuecomment-1139299194. What is the ETA for container images that can be consumed by end users?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[katexochen]

/remove-lifecycle stale

[aojea]

https://console.cloud.google.com/gcr/images/k8s-staging-cloud-provider-gcp/GLOBAL/cloud-controller-manager has the released images

 docker pull gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v26.2.4
v26.2.4: Pulling from k8s-staging-cloud-provider-gcp/cloud-controller-manager
fc251a6e7981: Already exists
1a8af71790f3: Already exists
db4f354738a1: Pull complete
Digest: sha256:e70becd7b8cc50a3ac80f36ad0db8781742a225563e759897f846ac728da87db
Status: Downloaded newer image for gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v26.2.4
gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v26.2.4

[ialidzhikov]

@aojea, are there also non-staging images?

[jingxu97]

/cc @msau42

[katexochen]

has the released images

There is only a single image that is not tagged as alpha. Also, the registry URL says staging, which suggests that these images shouldn't be used in production. If these are release images indeed, it would be great if they could be tagged with a release tag and be made available under the common URL that was used before: registry.k8s.io/cloud-controller-manager.

[aojea]

Sent https://github.com/kubernetes/k8s.io/pull/5231 to promote the image

[aojea]

here you go folks

docker pull registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v26.2.4
v26.2.4: Pulling from cloud-provider-gcp/cloud-controller-manager
Digest: sha256:e70becd7b8cc50a3ac80f36ad0db8781742a225563e759897f846ac728da87db
Status: Image is up to date for registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v26.2.4
registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v26.2.4

[aojea]

@justinsb you may be interested in this too ^^^

[ialidzhikov]

@aojea , thanks for the effort.

What is the reasoning behind the tag v26.2.4? Does it mean that this CCM vendors k8s.io v0.26.x and is mainly compatible with K8s 1.26? I could suggest to follow the versioning policy of the other CCMs. They all release versions like v1.25.x, v1.26.x, v1.27.x where the minor version of the CCM corresponds to the K8s version it vendors. In this way it is much easier to track the things and to use the proper CCM version according to the K8s version of your cluster. tl;dr v1.26.x is much more intuitive than v26.2.4.

Shouldn't we also have a corresponding github release? Currently I only see tags but no github release. Do you also plan to release CCM versions that support (and vendor) K8s 1.24, 1.25, 1.27?

PS. I am not grumpy, just wanted to provide a constructive feedback.

[aojea]

PS. I am not grumpy, just wanted to provide a constructive feedback.

lol, I know I know, don't worry for my comment from the other issue, that was a misunderstanding

Shouldn't we also have a corresponding github release? Currently I only see tags but no github release.

yes, we should

What is the reasoning behind the tag v26.2.4? Does it mean that this CCM vendors k8s.io v0.26.x and is mainly compatible with K8s 1.26?

honestly I don't know, @sdmodi @jprzychodzen do we have some special meaning for the tags

[katexochen]

@aojea Thanks! Could you also add the v27.1.0 release to the registry?

[jprzychodzen]

What is the reasoning behind the tag v26.2.4?

Actually, that was my mistaken when creating tag v26.4.0

Regarding naming schema - when I was adding recent tags I was following convention set by previous maintainers.

Single patch release of the K8s (eg. v1.2.3) will create a specific tag in cloud-provider-gcp repo (v2.3.0 for our example). If we will need to improve CCM between patch releases of the K/K, we can use patch number to indicate another release (v2.3.1 in this case).

[takirala]

@jprzychodzen are there any plans to retag v26.2.4 as v26.4.0 (not saying/requesting it needs to be done, just curious as to what i should be using) ?

[jprzychodzen]

I've removed tag v26.2.4 and tag v26.4.0 is in place.

[itspngu]

I've removed tag v26.2.4 and tag v26.4.0 is in place.

@jprzychodzen could you please check again? Thanks.

$ regctl tag list registry.k8s.io/cloud-provider-gcp/cloud-controller-manager
sha256-e70becd7b8cc50a3ac80f36ad0db8781742a225563e759897f846ac728da87db.sig
v26.2.4

Edit: It seems you were talking about git tags, not container images. Unfortunately we're now in a situation where the only published image doesn't have a tagged version of manifests to go with it, could somebody look into publishing an image for v26.4.0 (and ideally v27.1.0 too, pretty please :))