There are no official published images for CCM #289

frezbo · 2021-11-05T10:27:44Z

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?

The text was updated successfully, but these errors were encountered:

zetaab · 2021-11-14T21:03:21Z

@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 · 2022-02-12T22:16:13Z

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 · 2022-02-14T11:04:44Z

/remove-lifecycle stale

pagottoo · 2022-03-09T21:17:56Z

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 · 2022-06-07T22:15:25Z

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 · 2022-06-17T21:01:20Z

/remove-lifecycle stale

ialidzhikov · 2022-06-17T21:02:18Z

/assign @jprzychodzen

ialidzhikov · 2022-06-17T21:03:05Z

/priority important-soon

ialidzhikov · 2022-07-20T10:19:49Z

ping @jprzychodzen

katexochen · 2022-10-06T09:30:08Z

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

jprzychodzen · 2022-12-23T00:13:54Z

/assign @aojea

I guess this has happened, right?

katexochen · 2022-12-23T09:50:05Z

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 · 2022-12-23T10:44:32Z

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 · 2023-02-06T12:32:29Z

I am bringing the topic raised in #300 (comment). What is the ETA for container images that can be consumed by end users?

k8s-triage-robot · 2023-05-07T12:44:01Z

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 · 2023-05-07T13:16:54Z

/remove-lifecycle stale

aojea · 2023-05-07T13:27:14Z

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 · 2023-05-07T14:40:14Z

@aojea, are there also non-staging images?

sdmodi · 2023-09-29T15:58:25Z

I don't have permissions to tag releases on this repository.

aojea · 2023-09-29T16:31:16Z

I don't have permissions to tag releases on this repository.

I see, let me redo the question, do we want to tag releases on this repo? do we want to adhere to a cadence? match kubernetes releases? ...
then we'll figure out the technical details, don't worry about that

sdmodi · 2023-09-29T16:36:54Z

It would be ideal to have periodic sync up with Kubernetes libraries and tag the releases accordingly. For example, in the current state we are synced up with k8s 1.28.0 when 1.28.2 is already available.

aojea · 2023-09-29T16:42:59Z

Ok, but what if we have a bug and we want to release something, what about v1.28.2-001 , where 001 is the patch release of ccm inside 1.28.2 ?

sdmodi · 2023-09-29T16:55:17Z

We can create a new tag for that. That would be ccm/v28.2.1. In this repo, the K8s minor version takes the major version tag. That leaves us the patch version for our internal changes.

aojea · 2023-09-29T16:57:42Z

sgtm, do you mind formalizing that submitting a PR , it just a brief doc or section in the README

sdmodi · 2023-09-29T16:58:37Z

I'll do that today.

sdmodi · 2023-09-29T21:00:06Z

#613

faiq · 2023-10-10T19:38:59Z

The images for v27.1.6 aren't available. Is there a work around I can use to get the images that are necessary?

itspngu · 2023-10-11T06:06:29Z

The images for v27.1.6 aren't available. Is there a work around I can use to get the images that are necessary?

You'd have to check out the corresponding git tag of this repo and build KCM/CCM from source yourself in the meantime.

cpanato · 2023-10-11T11:28:13Z

@sdmodi @aojea I think makes sense when we have a release publish the manifests in the github release, to make it easier to people to consume that.
I would not like to run bazel to build manifests locally, instead consume from upstream and adjust if needed

cpanato · 2023-10-11T11:44:48Z

also looks like this repo is tagged with ccm/tag_version and I think this will not build the expected image in cloudbuild, because the test-infra job will not be triggered with that tag: https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/k8s-staging-cloud-provider-gcp.yaml#L76

i can be totally wrong

faiq · 2023-10-11T23:05:03Z

I made a build process to do this and published here if anyone needs the GCP CPI :) https://github.com/mesosphere/cloud-provider-gcp/pkgs/container/cloud-controller-manager-gcp/136544418?tag=v27.1.6.d2iq.0

aojea · 2023-10-11T23:10:53Z

also looks like this repo is tagged with ccm/tag_version and I think this will not build the expected image in cloudbuild, because the test-infra job will not be triggered with that tag: https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/k8s-staging-cloud-provider-gcp.yaml#L76

i can be totally wrong

@cpanato I think you are right

faiq · 2023-10-12T02:59:41Z

I hope that does the trick! Please let us know if that ends up being the issue

aojea · 2023-10-13T06:21:09Z

crane ls  registry.k8s.io/cloud-provider-gcp/cloud-controller-manager
sha256-e70becd7b8cc50a3ac80f36ad0db8781742a225563e759897f846ac728da87db.sig
sha256-f057f6c934d6afa73a38f94b71d7da2f99033e9a6e689d59b4ee1e689031ef00.sig
v26.2.4
v27.1.6

latest release published

cpanato · 2023-10-13T08:01:02Z

@aojea nice! Can we have a release here in GitHub with the manifests as well?

aojea · 2023-10-13T17:55:43Z

@aojea nice! Can we have a release here in GitHub with the manifests as well?

what do you mean (more specifically)?

cpanato · 2023-10-13T18:37:53Z

@aojea nice! Can we have a release here in GitHub with the manifests as well?

what do you mean (more specifically)?

do we have any deployments/clusterrole/etc to publish as well? or just the image

itspngu · 2023-10-13T19:29:23Z

@aojea nice! Can we have a release here in GitHub with the manifests as well?

what do you mean (more specifically)?

do we have any deployments/clusterrole/etc to publish as well? or just the image

sort of

aojea · 2023-10-15T10:38:46Z

I see, that is #359

cpanato · 2023-10-20T08:14:21Z

oh bazel :)

andrewsykim · 2023-12-13T05:24:35Z

Is anyone working on addressing cpanto's comment about cloudbuild not recognizing our tagging format? I think we are still not publishing images on tagged releases

xrstf · 2024-01-12T13:15:16Z

The CCM image for Kubernetes 1.29.0 is not yet available / published, there's only

k8s-triage-robot · 2024-05-21T13:32:23Z

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

itspngu · 2024-05-21T13:45:25Z

/remove-lifecycle stale

frezbo mentioned this issue Nov 15, 2021

feat: add GCP ccm siderolabs/talos#4513

Merged

zetaab mentioned this issue Dec 13, 2021

Cut a release for K8s 1.23 #300

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2022

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 14, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 7, 2022

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 17, 2022

k8s-ci-robot assigned jprzychodzen Jun 17, 2022

k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 17, 2022

jprzychodzen mentioned this issue Nov 25, 2022

cloud-provider-gcp: periodically publish cloud-controller-manager image kubernetes/test-infra#27730

Closed

k8s-ci-robot assigned aojea Dec 23, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 7, 2023

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 7, 2023

ialidzhikov mentioned this issue Jan 12, 2024

Consider switching to the out-of-tree GCP cloud-controller-manager gardener/gardener-extension-provider-gcp#679

Open

aojea changed the title ~~published images~~ There are no official published images for CCM Feb 21, 2024

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 21, 2024

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 21, 2024

There are no official published images for CCM #289

There are no official published images for CCM #289

Comments

frezbo commented Nov 5, 2021

zetaab commented Nov 14, 2021 • edited

k8s-triage-robot commented Feb 12, 2022

zetaab commented Feb 14, 2022

pagottoo commented Mar 9, 2022

k8s-triage-robot commented Jun 7, 2022

ialidzhikov commented Jun 17, 2022

ialidzhikov commented Jun 17, 2022

ialidzhikov commented Jun 17, 2022

ialidzhikov commented Jul 20, 2022

katexochen commented Oct 6, 2022

jprzychodzen commented Dec 23, 2022

katexochen commented Dec 23, 2022

aojea commented Dec 23, 2022 • edited

ialidzhikov commented Feb 6, 2023

k8s-triage-robot commented May 7, 2023

katexochen commented May 7, 2023

aojea commented May 7, 2023

ialidzhikov commented May 7, 2023

sdmodi commented Sep 29, 2023

aojea commented Sep 29, 2023

sdmodi commented Sep 29, 2023

aojea commented Sep 29, 2023

sdmodi commented Sep 29, 2023

aojea commented Sep 29, 2023 • edited

sdmodi commented Sep 29, 2023

sdmodi commented Sep 29, 2023

faiq commented Oct 10, 2023

itspngu commented Oct 11, 2023

cpanato commented Oct 11, 2023

cpanato commented Oct 11, 2023 • edited

faiq commented Oct 11, 2023

aojea commented Oct 11, 2023

faiq commented Oct 12, 2023

aojea commented Oct 13, 2023

cpanato commented Oct 13, 2023

aojea commented Oct 13, 2023

cpanato commented Oct 13, 2023

itspngu commented Oct 13, 2023

aojea commented Oct 15, 2023

cpanato commented Oct 20, 2023

andrewsykim commented Dec 13, 2023 • edited

xrstf commented Jan 12, 2024

k8s-triage-robot commented May 21, 2024

itspngu commented May 21, 2024

zetaab commented Nov 14, 2021 •

edited

aojea commented Dec 23, 2022 •

edited

aojea commented Sep 29, 2023 •

edited

cpanato commented Oct 11, 2023 •

edited

andrewsykim commented Dec 13, 2023 •

edited