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

IPv6 integration tests #1658

Merged
merged 2 commits into from
Oct 4, 2021
Merged

Conversation

achevuru
Copy link
Contributor

@achevuru achevuru commented Oct 4, 2021

What type of PR is this?
feature tests

What does this PR do / Why do we need it:
PR adds integration tests for IPv6 support.

Testing done on this change:
Verified the ipv6 integration test suite on an IPv6 cluster.

Automation added to e2e:
Yes. test/integration-new/cni/ipv6

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
N/A

Does this change require updates to the CNI daemonset config files to work?:

Does this PR introduce any user-facing change?:


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.


for _, pod := range podNetworkingValidationInput.PodList {

podIP, podIPNet, err := net.ParseCIDR(pod.PodIPv4Address + "/32")
podIP = pod.PodIPv4Address
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Looks like indentation is bit off.

@@ -40,8 +41,10 @@ func main() {
StartTCPServer(addr)
} else if serverMode == "udp" {
StartUDPServer(addr)
} else if serverMode == "http" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Need to update "// Supported modes are tcp, udp" for var serverMode string on line 29

// express or implied. See the License for the specific language governing
// permissions and limitations under the License.

package ipv6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe as a follow up can we also add test cases around the new env variables? ENABLE IPV4 and IPV6?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are covered by UT though. In general we can't toggle these 2 env variables on a live cluster as the cluster can either be an IPv4 or an IPv6 cluster.

Copy link
Contributor

@jayanthvn jayanthvn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@achevuru achevuru merged commit 0aa6baf into aws:release-1.10 Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants