Skip to content

Add acceptance test cases for multiport#5286

Open
shashankNandigama wants to merge 18 commits into
mainfrom
shashank/multiport-acceptance-tests
Open

Add acceptance test cases for multiport#5286
shashankNandigama wants to merge 18 commits into
mainfrom
shashank/multiport-acceptance-tests

Conversation

@shashankNandigama
Copy link
Copy Markdown
Contributor

@shashankNandigama shashankNandigama commented May 4, 2026

Changes proposed in this PR

Added multiport test-cases for meshGateway mode none.

How I've tested this PR

How I expect reviewers to test this PR

Checklist

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@shashankNandigama shashankNandigama force-pushed the shashank/multiport-acceptance-tests branch 3 times, most recently from 6c192a5 to 973a6a8 Compare May 7, 2026 12:05
@shashankNandigama shashankNandigama added backport/2.0.x Backport to release/2.0.x branch pr/no-changelog PR does not need a corresponding .changelog entry labels May 7, 2026
@shashankNandigama shashankNandigama force-pushed the shashank/multiport-acceptance-tests branch 2 times, most recently from 8de9ff7 to aa04fa5 Compare May 10, 2026 10:09
@shashankNandigama shashankNandigama marked this pull request as ready for review May 11, 2026 13:59
@shashankNandigama shashankNandigama requested review from a team as code owners May 11, 2026 13:59
@shashankNandigama shashankNandigama changed the title DO NOT MERGE Add acceptance test cases for multiport Add acceptance test cases for multiport May 11, 2026
@shashankNandigama shashankNandigama force-pushed the shashank/multiport-acceptance-tests branch 4 times, most recently from 9215da5 to 5ce9ccc Compare May 15, 2026 08:15
On Kind, the install-cni container copies the consul-cni binary twice:
once immediately on startup, and once again after a 100-second grace
period. The second copy pushes memory usage above the default 100Mi
limit, triggering an OOMKill before the ZZZ-consul-cni-kubeconfig and
the chained conflist entry can be written to /etc/cni/net.d/. Without
those files kubelet never invokes the consul-cni plugin, so pods on that
node receive no tproxy iptables rules. This causes inbound mTLS
connections from the client sidecar to reach the application directly
instead of being redirected to Envoy, returning a TLS WRONG_VERSION_NUMBER
error that does not match any failureMessage and hangs the test.

Raise the memory limit to 200Mi and request to 150Mi so the install
completes successfully on Kind clusters.
@shashankNandigama shashankNandigama force-pushed the shashank/multiport-acceptance-tests branch from 9aaa1b5 to 23b36e2 Compare May 27, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/2.0.x Backport to release/2.0.x branch pr/no-changelog PR does not need a corresponding .changelog entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant