Kops: kubeadm support for bootstrapping clusters

Created on 10 Feb 2017  路  12Comments  路  Source: kubernetes/kops

This is an issue to track the progress of supporting kubeadm (link) as a cluster bootstrap avenue for kops.

Success Criteria (Day 1)

  1. Specify a command line flag to instruct kops to use kubeadm in place of nodeup
  2. The feature will be experimental, and will not be advertised as production ready.
  3. The new bootstrap avenue will need a name to be compatible with Cloud Formation https://github.com/kubernetes/kops/issues/1841

Future considerations

Output
  1. We will need to come up with a clever name for bootstrap avenue. This will probably manifest itself as a command line flag, as well as an API parameter for kops. Respond below with suggestions please!
  2. We will need to determine how to advertise this as an experimental feature of kops. Again, suggestions below please!

CC @jbeda @justinsb

lifecyclfrozen

Most helpful comment

馃憤
bootstrap channel?

All 12 comments

馃憤
bootstrap channel?

Is this plan still active?

@bhack the kubeadm team is looking at breaking up kubeadm into usable parts, but at this point we are not able to.

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

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
/remove-lifecycle stale

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

/reopen

You can absolutely use phases now that kubeadm is GA.

@timothysc: Reopened this issue.

In response to this:

/reopen

You can absolutely use phases now the kubeadm is GA.

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.

/lifecycle frozen

Hello, is there a plan for replacing nodeup/protokube with kubeadm?

Should happen as part of adopting the cluster-api.

We're also gradually more and more stuff out of nodeup/protokube - e.g. to etcdadm, addon-manager etc

Thanks a lot @justinsb. So is there a design doc or discussion email thread for how to adopting the cluster-api? I鈥榤 seeking for an easy to use CLI to deploy K8s on vSphere. kops has a nice CLI and vSphere provider in alpha, but seems it's not maintained any more.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

thejsj picture thejsj  路  4Comments

drewfisher314 picture drewfisher314  路  4Comments

joshbranham picture joshbranham  路  3Comments

Caskia picture Caskia  路  3Comments

justinsb picture justinsb  路  4Comments