-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
area/agentCilium agent related.Cilium agent related.area/helmImpacts helm charts and user deployment experienceImpacts helm charts and user deployment experiencegood-first-issueGood starting point for new developers, which requires minimal understanding of Cilium.Good starting point for new developers, which requires minimal understanding of Cilium.help-wantedPlease volunteer for this by adding yourself as an assignee!Please volunteer for this by adding yourself as an assignee!kind/featureThis introduces new functionality.This introduces new functionality.
Description
In the install documentation for EKS, it has you manually remove some stale AWS iptables rules. Not removing these rules results in subtle and random connectivity issues, most notably around host-network processes accessing the pod network. This typically results in a failure to reach the health check.
So, when we're sure these aren't in use, we should remove these in the nodeinit script.
The challenge is knowing these rules are not in use. From reading the install documentation, I don't see a reliable way to detect it, so we'll have to add another helm value. Probably something like nodeinit.removeAWSCNI
.
Metadata
Metadata
Assignees
Labels
area/agentCilium agent related.Cilium agent related.area/helmImpacts helm charts and user deployment experienceImpacts helm charts and user deployment experiencegood-first-issueGood starting point for new developers, which requires minimal understanding of Cilium.Good starting point for new developers, which requires minimal understanding of Cilium.help-wantedPlease volunteer for this by adding yourself as an assignee!Please volunteer for this by adding yourself as an assignee!kind/featureThis introduces new functionality.This introduces new functionality.
Type
Projects
Status
Done