Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

🌱 Migrate Control Plane Image to include "cluster-api" in the name #117

Open
christopherhein opened this issue Jun 9, 2021 · 5 comments
Open

🌱 Migrate Control Plane Image to include "cluster-api" in the name #117

christopherhein opened this issue Jun 9, 2021 · 5 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
next

Comments

@christopherhein
Copy link
Contributor

See https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-cluster-api-nested/images.yaml for officially pushed images. The nested-controlplane-controller resource should be cluster-api-nested-controlplane-controller.
@christopherhein
Copy link
Contributor Author

/milestone next
/kind cleanup

@k8s-ci-robot k8s-ci-robot added this to the next milestone Jun 9, 2021
@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jun 9, 2021
@christopherhein
Copy link
Contributor Author

/retitle 🐛 Migrate Control Plane Image to include "cluster-api" in the name

@k8s-ci-robot k8s-ci-robot changed the title Migrate Control Plane Image to include "cluster-api" in the name 🐛 Migrate Control Plane Image to include "cluster-api" in the name Jun 15, 2021
@christopherhein
Copy link
Contributor Author

/retitle 🌱 Migrate Control Plane Image to include "cluster-api" in the name

@k8s-ci-robot k8s-ci-robot changed the title 🐛 Migrate Control Plane Image to include "cluster-api" in the name 🌱 Migrate Control Plane Image to include "cluster-api" in the name Jun 15, 2021
@k8s-triage-robot
Copy link

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

@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 Sep 13, 2021
@christopherhein
Copy link
Contributor Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
next
Development

No branches or pull requests
3 participants
@christopherhein @k8s-ci-robot @k8s-triage-robot