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 ClusterVersion from vc-manager & native provisioner. #131
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
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 13, 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 13, 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 a user I would like to reduce the overall components deployed for using CAPN w/ VC so I don't need to support deprecated provisioning routes.
Detailed Description
With the move to support CAPN, provisioning should be done outside of VC drawing a hard line between CAPN and VC, with this move we'll be able to get vc-manager and the
controller-gen
manifests back to being auto generated and easily consumed.Anything else you would like to add:
This should help to remove cruft that made #62 and #63 hard to configured and causes user confusion.
[Miscellaneous information that will assist in solving the issue.]
/kind feature
/milestone v0.1.x
The text was updated successfully, but these errors were encountered: