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

Kubespray Operator #5516

Closed
12 tasks
riverzhang opened this issue Jan 8, 2020 · 10 comments
Closed
12 tasks

Kubespray Operator #5516

riverzhang opened this issue Jan 8, 2020 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@riverzhang
Copy link
Contributor

riverzhang commented Jan 8, 2020

What would you like to be added:
This issue talk about for defining the kubespray operator, a tool for enabling declarative control of kubespray workflows, automating the execution and the orchestration of workflow tasks across existing nodes in a cluster or install a new cluster.
Why is this needed:
it is a kubernetes operator deploy in meta kubernetes and manage all kubernetes clusters(create、scale、delete、upgrade、 fault self-healing, etc.)
Tracking issue for tasks.

  • Kubespray Operator Design document
  • Create a new Kubespray Operator project?
  • Support etcd 3.4.x
  • Redeploy kubernetes Certificates
  • Offline Environment
  • Split kubespray ansible tasks, each repeatable configuration, Including etcd, container engine, network plugin etc
  • Change configuration in an existing cluster, base of ansible and kubeadm
  • Arm support
  • Use kubebuilder 2.0 to create operator framework
  • kubespray-cli is a command line tool written in Go,Base of asnbile and kubeadm. example tk8
  • First support bare metal, then cloud platforms.
  • Switch to ComponetConfig in the future, Make it easy for a component to correctly adopt ComponentConfig (encoding/decoding/flag merging).
@riverzhang riverzhang added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 8, 2020
@mattymo
Copy link
Contributor

mattymo commented Jan 8, 2020

Ideally it should implement k8s cluster API or be as close as possible to it. I think it can start in contrib/ directory, but if it gets larger, we will decide where to locate it.

@xiaohuanxj
Copy link

Redeploy kubernetes Certificates

@riverzhang
Copy link
Contributor Author

kubernetes/kubeadm#581

@jseguillon
Copy link
Contributor

FYI : an Ansible Operator already exists => https://github.com/operator-framework/operator-sdk . May be a good starter to write down this kubespray operator ?

@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-testing, kubernetes/test-infra and/or fejta.
/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 Jun 11, 2020
@riverzhang
Copy link
Contributor Author

@jseguillon Thanks,awesome.

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 18, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

@panpan0000
Copy link
Contributor

@riverzhang

"kubean" is a operator for kubespray , providing declarative CRD to manage cluster life cycle.

you can find it here https://github.com/kubean-io/kubean

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/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

7 participants