-
Notifications
You must be signed in to change notification settings - Fork 36
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
Disable SrcAndDestCheck on NAT Instances #39
Conversation
9d61b0c
to
dc682b8
Compare
/invite @DockToFuture @ScheererJ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/needs second-opinion |
/assign @ScheererJ @DockToFuture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor NIT.
/lgtm otherwise.
/squash
@ScheererJ You have pull request review open invite, please check |
e858e0b
to
f509dce
Compare
f509dce
to
aa405e6
Compare
What this PR does / why we need it:
This PR is needed to support calico's "CrossSubnet" mode on gardener clusters for provider type
aws
the src and dst checks. This PR introduces a new boolean field in the providerSpec of the MachineClass for AWS calledSrcAndDstChecksEnabled
which when set tofalse
disabled theSrcAndDestCheck
on that AWS EC2 instance.Which issue(s) this PR fixes:
Fixes #36
Special notes for your reviewer:
Release note:
A new boolean field called `SrcAndDstChecksEnabled` in the providerSpec of the MachineClass for AWS is introduced. The default value of this flag is `true` which retains current behavior. However, on setting this flag to `false` these checks are disabled.