Update Kubernetes docs to reflect that pods aren't "Ready" before init #3291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
jseldess
approved these changes
Jun 21, 2018
This is true as of the updates that we made to the Kubernetes config for v2.0.
a-robinson
force-pushed
the
k8s-readiness
branch
from
31c018f
to
26a4baf
Compare
|
I've gone and added a note to the initialization step that the pods should now be ready. Still look ok? |
|
Still LGTM. Thanks, @a-robinson! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is true as of the updates that we made to the Kubernetes config for
v2.0.