-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add dualstack test to validate k3s issue 10053 #106
Conversation
hey Max, when are these tests being run? I know about the e2e tests being run nightly but I was not aware of these |
These are the tests that QA runs in Jenkins and locally during patch testing/issue validation, using real environments (instances in AWS) to match what users are likely doing |
Signed-off-by: rancher-max <max.ross@suse.com>
Signed-off-by: rancher-max <max.ross@suse.com>
Signed-off-by: rancher-max <max.ross@suse.com>
Signed-off-by: rancher-max <max.ross@suse.com>
ae54597
to
5f01218
Compare
Signed-off-by: rancher-max <max.ross@suse.com>
Signed-off-by: rancher-max <max.ross@suse.com>
func TestIngressWithPodRestartAndNetPol(cluster *factory.Cluster, deleteWorkload bool) { | ||
// Deploy server and client pods | ||
err := shared.ManageWorkload("apply", "k3s_issue_10053_ns.yaml", | ||
"k3s_issue_10053_pod1.yaml", "k3s_issue_10053_pod2.yaml") |
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.
I like this reference to issue
Proposed Changes
Added dualstack test to validate issue
Types of Changes
issue validation
Testing
Checklist:
If your PR changes anything on or related to Jenkins, run it pointing to your branch to make sure it's okay.
✅
Verify code lint; we should not have errors.
✅
Update the documentation if needed.
N/A
Update makefile and docker run if adding new tests.
N/A
Run your tests at least 4 times with all configurations needed and possible.
✅
If needed test with different os types.
✅
Linked Issues
k3s-io/k3s#10053
Further Comments
@rbrtbnfgl @manuelbuil -- adding you both as reviewers to generally make sure the steps are as expected in
pkg/testcase/dualstack.go
I can confirm when running via a recent commitid where it is fixed this works as expected:
Working log snippet
And when using the previous released version (v1.30.1+k3s1) this fails as expected:
Failing log snippet