-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Replace containervm with GCI as default master image for GCE clusters #26197
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,11 +35,20 @@ PREEMPTIBLE_NODE=${PREEMPTIBLE_NODE:-false} | |
PREEMPTIBLE_MASTER=${PREEMPTIBLE_MASTER:-false} | ||
|
||
|
||
OS_DISTRIBUTION=${KUBE_OS_DISTRIBUTION:-debian} | ||
MASTER_IMAGE=${KUBE_GCE_MASTER_IMAGE:-container-vm-v20160321} | ||
# Today the cluster startup scripts asssume the master and the nodes use the | ||
# same OS distro, thus same set of initialization instructions (e.g., metadata, | ||
# startup scripts, etc.). The current workaround is the hack in util.sh that | ||
# reloads <os_distro>/helper.sh in the gap between when the master is created | ||
# and when the nodes are created. | ||
# TODO(#26183): Provide a way to differentiate master OS distro and node OS | ||
# distro. | ||
OS_DISTRIBUTION=${KUBE_OS_DISTRIBUTION:-gci} | ||
# For GCI, leaving it blank will auto-select the latest GCI image on the `dev` | ||
# channel. | ||
MASTER_IMAGE=${KUBE_GCE_MASTER_IMAGE:-} | ||
MASTER_IMAGE_PROJECT=${KUBE_GCE_MASTER_PROJECT:-google-containers} | ||
NODE_IMAGE=${KUBE_GCE_NODE_IMAGE:-"${MASTER_IMAGE}"} | ||
NODE_IMAGE_PROJECT=${KUBE_GCE_NODE_PROJECT:-"${MASTER_IMAGE_PROJECT}"} | ||
NODE_IMAGE=${KUBE_GCE_NODE_IMAGE:-container-vm-v20160321} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a reason why this shouldn't be blank as well to default to the latest dev channel image? Why do that for master and not node? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oops, I realize now that gci != containervm, I guess a better question is "what's the reason for not having both be gci".. a comment indicating if this is temporary would be helpful. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. See #26316 |
||
NODE_IMAGE_PROJECT=${KUBE_GCE_NODE_PROJECT:-google-containers} | ||
CONTAINER_RUNTIME=${KUBE_CONTAINER_RUNTIME:-docker} | ||
RKT_VERSION=${KUBE_RKT_VERSION:-0.5.5} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why change this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because now that
OS_DISTRIBUTION
defaults togci
, one doesn't have to setKUBE_OS_DISTRIBUTION
any more to start a GCI cluster. In that case, the old logic would fail.For other distros on this list, they all have to set
KUBE_OS_DISTRIBUTION
as before, butOS_DISTRIBUTION
will always equal toKUBE_OS_DISTRIBUTION
, so it should work for them too. Are you thinking of anything that could potentially break because of this change?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that
OS_DISTRIBUTION
defaults togci
, one doesn't have to setKUBE_OS_DISTRIBUTION=gci
any more to start a GCI cluster, and the old logic will start to fail in this case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for explaining. I was concerned it wasn't set in all paths that call this, but on looking more it looks fine.