-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Support Cluster-API standard #9652
Comments
relevant to #8753 |
@panpan0000 Could you describe what feature do you mean Do you want to deploy Cluster-API itself from Kubespray? |
just a raw expectation : User could interface with cluster-API standard CRD, but the underlaying logic are all implemented by kubespray. just two cents, not come to implementation solution so far. |
echo.. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
I think this is a very valuable work and I am happy to participate. |
I think we need design some parts,like
|
Cluster-api working group is thinking about In-place upgrades feature. |
/remove-lifecycle stale |
It's doubtful that Kubespray could (or should) support clusterAPI. We're not a cloud provider, and there is no API running on some server. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What would you like to be added:
to implement part or full clusterAPI standard.
Why is this needed:
In Cloud Native World, declarative API is the trend.
I found kubean project already provides k8s-operator for kubespray so far.
Additionally, But if clusterAPI can be supported, it maybe another good thing to community.
Is there any scope conflict or technical obstacle ?
The text was updated successfully, but these errors were encountered: