kubeadm#33262
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
|
I am okay with these commits being contributed to Google. |
|
I am okay with these commits being contributed to Google. |
1 similar comment
|
I am okay with these commits being contributed to Google. |
|
|
||
| - `--token=<token>` | ||
|
|
||
| By default, a token is generated, but if you are to automate cluster deployment, you will want to |
There was a problem hiding this comment.
indent the paragraph and you get nice alignment with the flag.
| By default, `kubeadm` sets `cluster.local` as the cluster DNS domain. If you would like to set a different one, use `--service-dns-domain`. | ||
|
|
||
| - `--schedule-workload=<bool>` (default: "false") | ||
|
|
There was a problem hiding this comment.
strange flag name. Why not be more explicit: --master-schedulable
There was a problem hiding this comment.
Good question, I am not entierely sure why we ended-up with this exact flag. @lukemarsden might have some background on this.
There was a problem hiding this comment.
There was a discussion on sig-cluster-lifecycle about that. We were not certain about the usage of word schedulable so we ended up with schedule-workload.
There was a problem hiding this comment.
on balance i think --master-schedulable is better, i'd be happy to change this but let's be quick about it
There was a problem hiding this comment.
Also, -S alias would probably make sense. To be very honest, I struggle to spell "schedulable", pronouncing it is even harder. On that note, I am okay to change it, but may be we can think of something a bit better? For example, --accept-workload may be a good one to consider.
There was a problem hiding this comment.
+1 to --accept-workload.
I'm not sure about the usage of term master here, because init is run on master, in case if we are fine with term "schedulable" in user facing interface, I would probably just rename it to --schedulable.
There was a problem hiding this comment.
Without the word "master" it's not clear to me that this only applies to the master nodes. We are initializing the cluster. So flags might have a cluster-wide influence.
There was a problem hiding this comment.
Let's go with --schedule-pods-here.
There was a problem hiding this comment.
I'll be looking out for having a reverse one for nodes, cause you might wanna have spare nodes that initially don't take any workload until you turn the knob. I mean: kubeadm join --schedule-pods-here=false.
|
I am okay with these commits being contributed to Google. |
|
|
||
| cmdutil "k8s.io/kubernetes/pkg/kubectl/cmd/util" | ||
| "k8s.io/kubernetes/pkg/util/flag" | ||
|
|
There was a problem hiding this comment.
Ah, there is also a bit of junk down below, I completely forgot to look at this doc, I'll go and cleanup now! (this was in relation to the readme)
068d400 to
d08bdf9
Compare
| @@ -0,0 +1,94 @@ | |||
| # Kubernetes Cluster Boostrap Made Easy | |||
|
I am okay with these commits being contributed to Google. |
|
_Docs: kubernetes/website#1265_ |
|
|
||
| By default, when `kubeadm init` runs, a token is generated and revealed in the output. That's the token you should use here. | ||
|
|
||
| ## User Experience Considerations (move to design doc, when we have one) |
There was a problem hiding this comment.
let's just delete this section
| "host_pki_path": "/etc/kubernetes/pki", | ||
| "host_etcd_path": "/var/lib/etcd", | ||
| "hyperkube_image": "", | ||
| "discovery_image": "dgoodwin/kubediscovery:latest", // TODO(phase1): fmt.Sprintf("gcr.io/google_containers/kube-discovery-%s:%s", runtime.GOARCH, "1.0"), |
There was a problem hiding this comment.
this is blocked on #32203 and getting this image into gcr.io I think
There was a problem hiding this comment.
or we can leave this as-is and do a followup PR once #32203 is ready, that would be fine too IMO
There was a problem hiding this comment.
PR is merged, as soon as @mikedanese has pushed the images, update
There was a problem hiding this comment.
Could you please confirm exact image with the tag and I'll update this?
There was a problem hiding this comment.
The format in the TODO looks correct. I can confirm later.
There was a problem hiding this comment.
Doesn't look it's present, I've tried different tags and cannot remember how to list tags. In fact, I am not even sure how to confirm gcr.io/google_containers/kube-apiserver-amd64 exist at all.
There was a problem hiding this comment.
@errordeveloper https://gcr.io/v2/google-containers/kube-discovery-amd64/tags/list
I'll include it in my new patch
Thanks @mikedanese!
lukemarsden
left a comment
There was a problem hiding this comment.
couple of review comments
d0b1e5c to
65ced26
Compare
|
Thanks @luxas and everyone else! |
|
And no other PRs in SQ! That's great |
|
@k8s-bot gke e2e test this |
|
Jenkins verification failed for commit 1cf13343d0c3a7c22b02b095f02be2e0f464ae66. Full PR test history. The magic incantation to run this job again is |
|
Please drop merge commits. |
c48ee19 to
3a4613d
Compare
Done. |
|
Jenkins GCI GKE smoke e2e failed for commit 3a4613d. Full PR test history. The magic incantation to run this job again is |
|
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
|
Jenkins GKE smoke e2e failed for commit 3a4613d. Full PR test history. The magic incantation to run this job again is |
|
Automatic merge from submit-queue |
|
Mike, do you have any poi gets to docs to confirm that? On Tue, 27 Sep 2016, 11:53 Mike Danese, [email protected] wrote:
|
Automatic merge from submit-queue Start tidying kubeadm up **What this PR does / why we need it**: This PR addresses kubernetes#33262 (comment). **Release note**: ```release-note NONE ```
What this PR does / why we need it:
This PR add alpha version of
kubeadmtool, which allows user to boostrap a cluster rather quite easily. This is the initial contribution from @kubernetes/sig-cluster-lifecycle members, who's aim is to build easy-to-use tools that help to operate a cluster throughout its lifetime.Which issue this PR fixes: a leap towards kubernetes/enhancements#11
Special notes for your reviewer: previously seen by many folks in #31221
Release note:
This change is