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
fix(firewall): open node to master ICMP security group #15339
base: master
Are you sure you want to change the base?
fix(firewall): open node to master ICMP security group #15339
Conversation
|
Welcome @maximumG! |
Hi @maximumG. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Cilium health check mechanism requires ICMP and TCP/4240 port to be opened between every node in the cluster including control plane nodes. If one of these 2 checks fails the node is considered as unreachable.
7f5b0dd
to
6853955
Compare
Thanks. I think I am somewhat convinced it is practical to allow this traffic. /ok-to-test |
You probably need to run |
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.
weird to see a change in here, especially regading the protocol parameter, switching from a valid value 4 to -1 🤔 . Any idea why this may happened @olemarkus
from_port = 0 | ||
protocol = "4" | ||
security_group_id = aws_security_group.masters-privatecalico-example-com.id | ||
protocol = "-1" |
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.
weird to see a change in here, especially regading the protocol parameter, switching from a valid value 4 to -1 🤔 . Any idea why this may happened @olemarkus
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.
It's an artifact of the diff. Changing "4" to "ipip" caused that rule to sort after the "all-0to0-nodes" rule.
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.
some calico related test are failing because the integration tests were modified and the ipip protocol switch from value 4 to -1.
/retest |
@olemarkus is there any way I can help to finalize this PR ? |
@@ -1029,6 +1029,15 @@ resource "aws_security_group_rule" "from-nodes-minimal-ipv6-example-com-ingress- | |||
type = "ingress" | |||
} | |||
|
|||
resource "aws_security_group_rule" "from-nodes-minimal-ipv6-example-com-ingress-icmp-8to8-masters-minimal-ipv6-example-com" { | |||
from_port = 8 |
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.
ICMPv6 echo is not type 8.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
switch protocol { | ||
case ProtocolIPIP: | ||
name = "ipip" | ||
awsName = "ipip" |
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.
ipip
is not a valid value for the IpProtocol
field of an IpPermission
.
// The IP protocol name (tcp, udp, icmp, icmpv6) or number (see Protocol Numbers
// (http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)).
Please test your change works on an IPv6 cluster. |
@maximumG: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@maximumG, may I inquire if there's a chance to consolidate or merge the changes? Your input would be greatly appreciated! |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Fixes #15329.
Cilium health check mechanism requires ICMP and TCP/4240 port to be opened between every nodes in the cluster, including control plane nodes. If one of these 2 checks fails the node is considered as unreachable.
We only open ICMP echo request (type 8) from node to master.