This repository was archived by the owner on Aug 18, 2025. It is now read-only.
clarify network policy implementations #203
Merged
Conversation
This file contains hidden or 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
Contributor
|
✨ Coder.com for PR #203 deployed! It will be updated on every commit.
|
khorne3
approved these changes
Mar 25, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
did some reading on network policy stuff, and learned that google enables Calico by default when
enable-network-policyis included in the create cluster command. added this clarification for GCP.additionally, azure has built-in support for calico, and users can only enable it upon cluster creation. added this clarification
as well, since we make no mention of Calico, outside of the
network-policy "calico"line in the create cluster command.open to thoughts & feedback.