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

AWS kube-up: tolerate a lack of ephemeral volumes #23776

Merged
merged 2 commits into from
Apr 2, 2016

Conversation

justinsb
Copy link
Member

@justinsb justinsb commented Apr 2, 2016

Some users have requested the ability to not use ephemeral volumes (local instance storage), but this also highlighted the fact that we likely fail to start on instance types with no instance storage (e.g. the c4 class instances).

Confirming this fix, and then going to confirm that e.g. c4 is broken. If so this will be a cherry-pick candidate.

format-disks used to run with non-strict bash semantics, but this changed in
1.2 as we now merge it into the GCE script, so pipefail and errexit are both
set.

However, the way we list the ephemeral disks, by piping to grep, would cause an
exit code of 2 if there were no ephemeral disks.

Tolerate failure here by add `|| true`.  The metadata service call is unlikely
to fail, so we continue to ignore that possibility.
We rename it to EPHEMERAL_BLOCK_DEVICE_MAPPINGS, and we also change the value
so that it starts with a `,`, instead of always inserting a comma before it.
In this way the value can be empty.

Also, if the user sets the (currently experimental) KUBE_AWS_STORAGE
environment variable to be "ebs", then we will not mount any instance storage
which will cause the machines to use EBS storage instead.
@k8s-github-robot
Copy link

Labelling this PR as size/S

@k8s-github-robot k8s-github-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. release-note-label-needed labels Apr 2, 2016
@k8s-bot
Copy link

k8s-bot commented Apr 2, 2016

GCE e2e build/test passed for commit f43f398.

@fagiani
Copy link

fagiani commented Apr 2, 2016

@justinsb, I have tested this PR with release 1.2.1, it works great using a cluster composed of 1 master and 2 host nodes all m3.medium.

Thanks a lot!

@justinsb
Copy link
Member Author

justinsb commented Apr 2, 2016

I'm marking this as a cherrypick-candidate, because it is not very invasive, and because we've had user friction with:

  1. not attaching any ephemeral volumes (kube-up attaches ephemeral volumes even when the instance type doesn't support it, which is harmless but wrong, which is how we "get away with it")
  2. the m3.medium instance type having 4GB, and users not wanting to use their local instance storage.

@k8s-cherrypick-bot
Copy link

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

@justinsb justinsb added this to the v1.2 milestone Apr 2, 2016
@eparis eparis added lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-label-needed labels Apr 2, 2016
@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit e9c57e6 into kubernetes:master Apr 2, 2016
@roberthbailey roberthbailey added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 6, 2016
zmerlynn added a commit that referenced this pull request Apr 6, 2016
…76-upstream-release-1.2

Automated cherry pick of #23776
@zmerlynn
Copy link
Member

zmerlynn commented Apr 6, 2016

@eparis: Any idea why cherrypick-candidate is still here?

@eparis
Copy link
Contributor

eparis commented Apr 7, 2016

@zmerlynn no, I have no idea. It looks like it should have been found/automatically cleaned up. I'll try to put it on my list of things to looks at.

shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
…ck-of-#23776-upstream-release-1.2

Automated cherry pick of kubernetes#23776
shouhong pushed a commit to shouhong/kubernetes that referenced this pull request Feb 14, 2017
…ck-of-#23776-upstream-release-1.2

Automated cherry pick of kubernetes#23776
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.