generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 65
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.
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
⚠️ Remove aliyun provisioner from vc-manager #132
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
Comments
k8s-ci-robot
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jun 15, 2021
/hold |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Sep 27, 2021
/remove-lifecycle stale |
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 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
User Story
As an operator I would like to separate provisioning from configuring VC to configure clusters so that I can individual manage components based on responsibility.
Detailed Description
With the move away from provisioning in VC and the addition of CAPI support #81 we should draw a harder line about the responsibilities of the
vc-manager
, instead of being responsible for provisioning it should shift to responsible for maintaining the VC state backed by anyCluster
object, this means we have to remove the native provisioned #131, as well as the aliyun provisioner, expecting VC to just maintain cluster stability from a CAPI CR.Anything else you would like to add:
This likely needs support to make sure clients previously using it get the same expectation and have a new provisioner route.
/kind feature
/milestone next
The text was updated successfully, but these errors were encountered: