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

Remove some prerequisites from single node docker cluster setup instructions. #18430

Merged

Conversation

fgrzadkowski
Copy link
Contributor

This is part of #18351.

Understanding and verifying those prerequisites is hard and according to @vishh now we will generate events and Node will be reported as NotReady (see #9837 (comment))

@asridharan @brendandburns

@k8s-github-robot
Copy link

Labelling this PR as size/M

@k8s-github-robot k8s-github-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 9, 2015
@k8s-bot
Copy link

k8s-bot commented Dec 9, 2015

GCE e2e test build/test passed for commit a5b2a7b8a1eac8e11555d73246cd456ab35c84a2.

@luxas
Copy link
Member

luxas commented Dec 9, 2015

I don't think this information should be removed totally.
For me, it was useful.
However, I agree that is don't have to be such big WARNING signals around (so users get scared), it would be fine with something smaller in the docs.
Maybe a place where you summarize docker requirements.

@@ -55,35 +55,7 @@ Here's a diagram of what the final result will look like:
### Prerequisites

1. You need to have docker installed on one machine.
2. Your kernel should support memory and swap accounting. Ensure that the
Copy link
Contributor

Choose a reason for hiding this comment

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

How about keeping this around for folks who have their nodes in-correctly configured. This information could reside in a Troubleshooting section for example :)

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree . This shouldn't be removed completely, but we can move it to the troubleshooting section.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm fine with moving this to Troubleshooting section. I just don't want to discourage people by seeing and reading a long and complicated list of kernel options.

@fgrzadkowski
Copy link
Contributor Author

@vishh Moved memsg/swap instructions to troubleshooting. PTAL.

@k8s-bot
Copy link

k8s-bot commented Dec 10, 2015

GCE e2e test build/test passed for commit b17c1cb.

@vishh
Copy link
Contributor

vishh commented Dec 10, 2015

Thanks @fgrzadkowski! These doc improvements are super helpful 💯

@vishh vishh added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 10, 2015
@k8s-github-robot
Copy link

Automatic merge from submit-queue

k8s-github-robot pushed a commit that referenced this pull request Dec 10, 2015
@k8s-github-robot k8s-github-robot merged commit c26a76d into kubernetes:master Dec 10, 2015
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request Mar 23, 2018
Automatic merge from submit-queue (batch tested with PRs 18666, 18810, 18430, 18517, 18653).

UPSTREAM: 59316: Exit if no client cert is available for 5m

Origin-commit: 0a8f794ba7c989ae6b798604f366d9ffb191ab98
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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants