Skip to content

Image registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v30.1.0 is missing #769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
dkoshkin opened this issue Oct 8, 2024 · 5 comments
Open

Image registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v30.1.0 is missing #769

dkoshkin opened this issue Oct 8, 2024 · 5 comments
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@dkoshkin
Copy link

dkoshkin commented Oct 8, 2024

The newest image is missing:

docker pull registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v30.1.0
Error response from daemon: manifest for registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v30.1.0 not found: manifest unknown: Failed to fetch "v30.1.0"
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 8, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2025
@YifeiZhuang
Copy link
Contributor

YifeiZhuang commented Feb 5, 2025 •
edited
Loading

There is no images published automatically on registry.k8s.io/cloud-provider-gcp/cloud-controller-manager
See: #289

Use this instead

docker pull gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:release-1.30(edited)

It looks we should do image promotions from gcr.io/k8s-staging* to registry.k8s.io:
https://github.com/kubernetes/k8s.io/tree/main/registry.k8s.io#managing-kubernetes-container-registries

@dkoshkin dkoshkin mentioned this issue Feb 5, 2025
Open
@YifeiZhuang YifeiZhuang mentioned this issue Feb 11, 2025
Closed
11 tasks
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 7, 2025
@kundan2707
Copy link

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 27, 2025
@kundan2707
Copy link

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@YifeiZhuang @dkoshkin @k8s-ci-robot @k8s-triage-robot @kundan2707