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

Jump to bottom

e2e test for mixed pods host-network true and false with external SNATing #816

Closed
jaypipes opened this issue Jan 29, 2020 · 9 comments
Closed

e2e test for mixed pods host-network true and false with external SNATing #816

jaypipes opened this issue Jan 29, 2020 · 9 comments
Labels
stale Issue or PR is stale testing

Comments

@jaypipes
Copy link
Contributor

Refer #519

We believe that pods with hostNetwork: true cause the CNI add API call to be bypassed, which means that the VPC CNI would not affect the data path at all for those pods. However, we should create and e2e scenario that tests the situation where, for example, an AWS VPC NAT Gateway is being used (and SNAT'ing traffic from pods on a particular subnet) and a worker node houses pods that have hostNetwork: true along with pods that do NOT have hostNetwork: true and ensure outbound communication works for both kinds of pods.
@jayanthvn jayanthvn assigned cgchinmay and unassigned abhipth Oct 19, 2021
@jayanthvn
Copy link
Contributor

We have added the test case for non-host networking pods. Will be extending that for host networking pods to complete the request in this issue.

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Apr 27, 2022
@jayanthvn
Copy link
Contributor

/not stale

@github-actions github-actions bot removed the stale Issue or PR is stale label Apr 28, 2022
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Jun 28, 2022
@jayanthvn
Copy link
Contributor

/notstale

@github-actions github-actions bot removed the stale Issue or PR is stale label Jun 29, 2022
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Oct 15, 2022
@github-actions
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2022
@jayanthvn jayanthvn reopened this Oct 30, 2022
@github-actions github-actions bot removed the stale Issue or PR is stale label Oct 31, 2022
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Dec 31, 2022
@github-actions
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale Issue or PR is stale testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jaypipes @jayanthvn @cgchinmay @abhipth @couralex6