Skip to content
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

Jump to bottom

Kubernetes Cluster Management API #2495

Closed
4 tasks
shekhar-rajak opened this issue Feb 12, 2021 · 13 comments
Closed
4 tasks

Kubernetes Cluster Management API #2495

shekhar-rajak opened this issue Feb 12, 2021 · 13 comments
Assignees
@fabriziopandini
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@shekhar-rajak
Copy link
Contributor

shekhar-rajak commented Feb 12, 2021 •
edited by neolit123

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.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 12, 2021
@shekhar-rajak
Copy link
Contributor Author

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

@neolit123 neolit123 added kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Feb 13, 2021
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 13, 2021
@neolit123
Copy link
Member

neolit123 commented Feb 13, 2021 •
edited

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.

@neolit123 neolit123 reopened this Mar 11, 2021
@draveness
Copy link
Contributor

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

@fabriziopandini
Copy link
Member

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
Copy link
Contributor

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
Copy link
Member

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

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2021
@vincepri
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2021
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2021
@fabriziopandini
Copy link
Member

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

@fabriziopandini
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 18, 2021
@vincepri
Copy link
Member

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
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fabriziopandini fabriziopandini

Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@neolit123 @vincepri @fabriziopandini @draveness @k8s-ci-robot @fejta-bot @k8s-triage-robot @shekhar-rajak