Kubernetes Cluster Management API

[ghost]

Enhancement Description

• One-line enhancement description (can be used as a release note): Kubernetes Cluster Management API
• Kubernetes Enhancement Proposal:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/clusterapi/2495-Kubernetes-Cluster-Management-API

We are building a set of Kubernetes cluster management APIs to enable common cluster lifecycle operations (install, upgrade, repair, delete) across disparate environments.
We represent nodes and other infrastructure in Kubernetes-style APIs to enable higher level controllers to update the desired state of the cluster (e.g. the autoscaling controller requesting additional machines) and reconcile the world with that state (e.g. communicating with cloud providers to create or delete virtual machines).
With the full state of the cluster represented as API objects, Kubernetes installers can use them as a common configuration language, and more sophisticated tooling can be built in an environment-agnostic way.

• Discussion Link:
• Primary contact (assignee): @vincepri @fabriziopandini
• Responsible SIGs: sig-cluster-lifecycle
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Implementation History

• December 2017 (KubeCon Austin): Prototype implementation on Google Compute Engine using Custom Resource Definitions

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[ghost]

Migrating all the old template keps to new template : #2493

[neolit123]

we can close this ticket as the original proposal was "accepted".

EDIT: actually let's keep this open in case CAPI bumps to beta and/or we update the design.

[draveness]

Do we have anyone working on this KEP? It seems no one is assigned.

[fabriziopandini]

I'm a CAPI maintainer, and we are pushing the project towards beta.
If this can help, I could act as a contact point here
/assign

[draveness]

I'm a CAPI maintainer, and we are pushing the project towards beta.
If this can help, I could act as a contact point here
/assign

Do you have any idea where I could see the related link and repo?

[fabriziopandini]

@draveness Cluster API project repo is https://github.com/kubernetes-sigs/cluster-api/

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[vincepri]

/remove-lifecycle stale

[k8s-triage-robot]

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

[fabriziopandini]

@vincepri I guess we should update/close this now...

[fabriziopandini]

/remove-lifecycle stale

[vincepri]

Sounds like we can go ahead and close this issue? The Cluster API project runs its own enhancement process through the form of CAEP(s), we might want to update the project status later on, although the process is already linked in https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/clusterapi

/close

[k8s-ci-robot]

@vincepri: Closing this issue.

In response to this:

Sounds like we can go ahead and close this issue? The Cluster API project runs its own enhancement process through the form of CAEP(s), we might want to update the project status later on, although the process is already linked in https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/clusterapi

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.