Open panpan0000 opened 1 year ago
@panpan0000 Could you describe what feature do you mean Support Cluster-API
here?
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. kubespray as an engine of cluster-api. it might be helpful for baremetal enviroments.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
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. https://github.com/kubernetes-sigs/cluster-api/pull/9559. maybe we need it.
/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. It's just a collection of ansible (which main point it to be agentless) roles which you apply to bring-up a cluster.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
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 ?