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

Update security_groups.md #8912

Merged
merged 3 commits into from
Apr 16, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/security_groups.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,10 @@ Kops will still output any differences in the managed and your own Security Grou
This is convenient for determining policy changes that need to be made when upgrading Kops.
**Using Managed Security Groups will not output these differences, it is up to the user to track expected changes to policies.**

*NOTE: Currently Kops only supports using existing Security Groups for every instance group and Load Balancer in the Cluster, not a mix of existing and managed Security Groups.
NOTE:
- *Currently Kops only supports using existing Security Groups for every instance group and Load Balancer in the Cluster, not a mix of existing and managed Security Groups.
This is due to the lifecycle overrides being used to prevent creation of the Security Groups related resources.*
- *Kops will still try to add necessary security group rules to the specified existing security group, despite that the name of field is "securityGroupOverride".*
zhming0 marked this conversation as resolved.
Show resolved Hide resolved

To do this first specify the Security Groups for the ELB (if you are using a LB) and Instance Groups
Example:
Expand Down