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.

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 ubuntu 22 and new make target for nft test #1757

Merged
merged 4 commits into from
Feb 15, 2023

Conversation

markapruett
Copy link
Member

Issue #, if available:
#1729

Description of changes:
Adds a new prow conformance test run using ubuntu 22 to test if ipv6 fails when the host is using iptables nft rules vs the legacy rules that our kube-proxy image is using.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@markapruett markapruett requested a review from jaxesn February 14, 2023 22:38
@danbudris
Copy link
Member

/lgtm

@markapruett
Copy link
Member Author

/approve

@markapruett
Copy link
Member Author

/approve

@eks-distro-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markapruett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@eks-distro-bot eks-distro-bot merged commit ed588e1 into aws:main Feb 15, 2023
danbudris pushed a commit to danbudris/eks-distro that referenced this pull request Sep 25, 2023
* Add ubuntu 22 and new make target for nft test

* Add prereqs correctly

* Add slash

* Run on AMD with ipv4 instead

---------

Co-authored-by: EKS Distro PR Bot <aws-model-rocket-bots+eksdistroprbot@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants