Thanks to visit codestin.com
Credit goes to github.com

Skip to content

kubeadm#33262

Merged
k8s-github-robot merged 32 commits into
kubernetes:masterfrom
errordeveloper:kubeadm
Sep 26, 2016
Merged

kubeadm#33262
k8s-github-robot merged 32 commits into
kubernetes:masterfrom
errordeveloper:kubeadm

Conversation

@errordeveloper
Copy link
Copy Markdown
Contributor

@errordeveloper errordeveloper commented Sep 22, 2016

What this PR does / why we need it:

This PR add alpha version of kubeadm tool, 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:

`kubeadm` (alpha) provides an easy way to securely bootstrap Kubernetes on Linux, see http://kubernetes.io/docs/kubeadm/

This change is Reviewable

@googlebot
Copy link
Copy Markdown

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.

@lukemarsden
Copy link
Copy Markdown
Contributor

I am okay with these commits being contributed to Google.

@k8s-github-robot k8s-github-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. release-note-label-needed labels Sep 22, 2016
@yoojinl
Copy link
Copy Markdown

yoojinl commented Sep 22, 2016

I am okay with these commits being contributed to Google.

1 similar comment
@pires
Copy link
Copy Markdown
Contributor

pires commented Sep 22, 2016

I am okay with these commits being contributed to Google.

Comment thread cmd/kubeadm/README.md Outdated

- `--token=<token>`

By default, a token is generated, but if you are to automate cluster deployment, you will want to
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indent the paragraph and you get nice alignment with the flag.

Comment thread cmd/kubeadm/README.md Outdated
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")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strange flag name. Why not be more explicit: --master-schedulable

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, I am not entierely sure why we ended-up with this exact flag. @lukemarsden might have some background on this.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on balance i think --master-schedulable is better, i'd be happy to change this but let's be quick about it

Copy link
Copy Markdown
Contributor Author

@errordeveloper errordeveloper Sep 23, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown

@yoojinl yoojinl Sep 23, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--schedule-pods-on-master

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's go with --schedule-pods-here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@luxas
Copy link
Copy Markdown
Member

luxas commented Sep 22, 2016

I am okay with these commits being contributed to Google.

Comment thread cmd/kubeadm/app/cmd/cmd.go Outdated

cmdutil "k8s.io/kubernetes/pkg/kubectl/cmd/util"
"k8s.io/kubernetes/pkg/util/flag"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • empty line

Copy link
Copy Markdown
Contributor Author

@errordeveloper errordeveloper Sep 22, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Comment thread cmd/kubeadm/README.md Outdated
@@ -0,0 +1,94 @@
# Kubernetes Cluster Boostrap Made Easy
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bootstrap

@taimir
Copy link
Copy Markdown
Contributor

taimir commented Sep 22, 2016

I am okay with these commits being contributed to Google.

@errordeveloper
Copy link
Copy Markdown
Contributor Author

_Docs: kubernetes/website#1265_

Comment thread cmd/kubeadm/README.md Outdated

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's just delete this section

Comment thread cmd/kubeadm/app/kubeadm.go Outdated
"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"),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is blocked on #32203 and getting this image into gcr.io I think

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or we can leave this as-is and do a followup PR once #32203 is ready, that would be fine too IMO

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR is merged, as soon as @mikedanese has pushed the images, update

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please confirm exact image with the tag and I'll update this?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The format in the TODO looks correct. I can confirm later.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

@lukemarsden lukemarsden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple of review comments

@luxas luxas removed the cla: no label Sep 25, 2016
@lukemarsden
Copy link
Copy Markdown
Contributor

Thanks @luxas and everyone else!

@luxas
Copy link
Copy Markdown
Member

luxas commented Sep 25, 2016

And no other PRs in SQ! That's great

@luxas luxas removed the cla: no label Sep 25, 2016
@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 25, 2016
@luxas luxas added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 25, 2016
@justinsb
Copy link
Copy Markdown
Member

@k8s-bot gke e2e test this

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Jenkins verification failed for commit 1cf13343d0c3a7c22b02b095f02be2e0f464ae66. Full PR test history.

The magic incantation to run this job again is @k8s-bot verify test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

@mikedanese
Copy link
Copy Markdown
Member

Please drop merge commits.

@lukemarsden
Copy link
Copy Markdown
Contributor

Please drop merge commits.

Done.

@luxas luxas added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed cla: no labels Sep 26, 2016
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Jenkins GCI GKE smoke e2e failed for commit 3a4613d. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

@k8s-github-robot
Copy link
Copy Markdown

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Jenkins GKE smoke e2e failed for commit 3a4613d. Full PR test history.

The magic incantation to run this job again is @k8s-bot gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

@k8s-github-robot
Copy link
Copy Markdown

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit c19e08e into kubernetes:master Sep 26, 2016
@errordeveloper
Copy link
Copy Markdown
Contributor Author

Mike, do you have any poi gets to docs to confirm that?

On Tue, 27 Sep 2016, 11:53 Mike Danese, [email protected] wrote:

@mikedanese commented on this pull request.

In cmd/kubeadm/app/api/types.go
#33262:

  •   }
    
  • }
  • Services struct {
  • CIDR      net.IPNet
    
  • DNSDomain string
    
  • }
  • PodNetwork struct {
  • CIDR net.IPNet
    
  • }
  • CloudProvider string
  • Schedulable bool
    +}
    +
    +const (
  • DefaultServiceDNSDomain = "cluster.local"
  • DefaultServicesCIDRString = "100.64.0.0/12"

Both AWS and Google networks use this range. This is going to cause weird
failures.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#33262, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS6gJKEwsWwyigzkctI6F1oMG74_uks5quPWxgaJpZM4KDq18
.

sttts pushed a commit to sttts/kubernetes that referenced this pull request Oct 24, 2016
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
```
@errordeveloper errordeveloper deleted the kubeadm branch January 9, 2018 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.