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.

Sign up for GitHub

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

Unbreak the EKS (tunnel) CI workflow reverting a no-longer necessary workaround #2273

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Unbreak the EKS (tunnel) CI workflow reverting a no-longer necessary workaround #2273

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 0 additions & 13 deletions .github/in-cluster-test-scripts/eks-tunnel.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,19 +25,6 @@ cilium status --wait
# Make sure the 'aws-node' DaemonSet exists but has no scheduled pods
[[ $(kubectl -n kube-system get ds/aws-node -o jsonpath='{.status.currentNumberScheduled}') == 0 ]]

# Clean up stale AWS-CNI iptables rules, which break host to pod connectivity (cilium/cilium#25804)
CLEANUP_CMD="\
iptables -t nat -F AWS-SNAT-CHAIN-0 && \
iptables -t nat -F AWS-SNAT-CHAIN-1 && \
iptables -t nat -F AWS-CONNMARK-CHAIN-0 && \
iptables -t nat -F AWS-CONNMARK-CHAIN-1"
kubectl get pod \
-n kube-system \
-l app.kubernetes.io/name=cilium-agent \
-o custom-columns=name:metadata.name --no-headers \
| xargs -I{} kubectl exec {} -n kube-system -c cilium-agent \
-- sh -c "$CLEANUP_CMD"

# Port forward Relay
cilium hubble port-forward&
sleep 10s
Expand Down
Loading