Skip to content

WINC-1778: [ote] Migrate networking tests to OTE (batch 2/6)#3922

Closed
weinliu wants to merge 1 commit intoopenshift:masterfrom
weinliu:WINC-1778-ote-batch2-networking
Closed

WINC-1778: [ote] Migrate networking tests to OTE (batch 2/6)#3922
weinliu wants to merge 1 commit intoopenshift:masterfrom
weinliu:WINC-1778-ote-batch2-networking

Conversation

@weinliu
Copy link
Copy Markdown
Contributor

@weinliu weinliu commented Apr 3, 2026

Summary

Migrates the Networking batch of WINC tests as part of WINC-1778.

Batch 2 — Networking (3 tests):

  • OCP-28632: Windows and Linux east-west network (uses pre-existing pods in winc-test)
  • OCP-32273: Configure kube proxy and external networking (LoadBalancer)
  • OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

Note: OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch due to its long runtime and disruptive nature.

Planned migration batches (WINC-1778):

Batch Category Tests Status
0 wmco golang version 37362 ✅ merged
1 (PR #3920) Node Basics 32554, 32615, 33612 🔄 in review
2 (PR #3922) Networking 28632, 32273, 31276 🔄 in review
3 (PR #3921) Logging & Monitoring 33779, 33783, 73595 🔄 in review
4 WICD, Workloads & Misc (no SSH) 50403, 60814, 25593, 42204, 38186 📋 planned
5 SSH-dependent tests 54711, 56354, 76765, 48873, 65980, 66670, 68320 ⏳ pending SSH decision
Special Needs special cluster 74760, 38188 ⏳ pending

Notes

  • OCP-28632 requires pre-existing win-webserver and linux-webserver pods in the winc-test namespace (provisioned by Flexy/cluster setup)
  • OCP-32273 skips on vsphere, nutanix, and platform=none (no LoadBalancer support)
  • OCP-31276 creates its own namespace and workloads, cleans up on completion

Summary by CodeRabbit

  • Tests
    • Added new Windows networking test suite covering East-West traffic validation between Windows and Linux workloads
    • Added external networking tests to verify LoadBalancer service functionality
    • Added internal networking tests validating CNI, multi-replica deployments, and cross-node cluster connectivity

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 3, 2026

@weinliu: This pull request references WINC-1778 which is a valid jira issue.

Details

In response to this:

Summary

Migrates the Networking batch of WINC tests as part of WINC-1778.

Batch 2 — Networking (3 tests):

  • OCP-28632: Windows and Linux east-west network (uses pre-existing pods in winc-test)
  • OCP-32273: Configure kube proxy and external networking (LoadBalancer)
  • OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

Note: OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch due to its long runtime and disruptive nature.

Planned migration batches (WINC-1778):

Batch Category Tests
1 Node Basics 32554, 32615, 33612
2 (this PR) Networking 28632, 32273, 31276
3 Logging & Monitoring 33779, 33783, 73595
4 WICD & Services 54711, 50403, 56354, 76765, 33794
5 Proxy 65980, 66670, 68320
6 Workloads & Misc 25593, 42204, 48873, 38186, 38188, 60814, 74760

Notes

  • OCP-28632 requires pre-existing win-webserver and linux-webserver pods in the winc-test namespace (provisioned by Flexy/cluster setup)
  • OCP-32273 skips on vsphere, nutanix, and platform=none (no LoadBalancer support)
  • OCP-31276 creates its own namespace and workloads, cleans up on completion

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 3, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 3, 2026

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: d6dc1ff3-8a00-48b8-8caf-96e7cfa7c931

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

The pull request introduces Windows networking extension tests to the WMCO test suite. A new batch of three extension test specs was registered in the test command module. These specs invoke corresponding extended networking checks that validate Windows pod communication patterns. A new networking check implementation file was created with three exported validation functions: one checking east-west pod-to-pod connectivity between Windows and Linux workloads, one validating external networking with LoadBalancer services, and one performing comprehensive CNI and internal networking validation across multiple connectivity paths including same-node and cross-node scenarios.

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name Status Explanation Resolution
Go Best Practices & Build Tags ⚠️ Warning Line 417 ignores errors with _ without justification, violating the core requirement. DNS constants hardcoded to winc-test are used in winc-31276 namespace tests, causing failures. Comment at line 415 is misleading. Add comment explaining error ignore at line 417; dynamically construct DNS names using namespace parameter; correct comment at line 415 to reflect Windows pod execution.
Platform-Specific Requirements ⚠️ Warning PR has DNS namespace hardcoding bug, missing platform-specific documentation, and misleading comments affecting test reliability. Fix DNS constants to use dynamic namespace variable, correct line 414 pod type comment, add platform-specific constraint documentation per platform (vSphere, AWS, Azure, GCP).
Windows Service Management ❓ Inconclusive PR implements Kubernetes networking tests for Windows containers on OpenShift; custom check requires Windows service management validation which is not applicable to this codebase. Custom check scope (Windows Service Control Manager, service dependencies, reboot handling) does not align with PR scope (Kubernetes networking, pod connectivity, CNI/DNS).
✅ Passed checks (2 passed)
Check name Status Explanation
Security: Secrets, Ssh & Csr ✅ Passed Comprehensive codebase analysis found no hardcoded secrets, credentials, or improper error logging patterns that expose sensitive data in credential handling, SSH connections, or CSR approval operations.
Kubernetes Controller Patterns ✅ Passed Pull request contains test infrastructure code, not Kubernetes controller implementation, making the check inapplicable to testing utilities.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 3, 2026

@weinliu: This pull request references WINC-1778 which is a valid jira issue.

Details

In response to this:

Summary

Migrates the Networking batch of WINC tests as part of WINC-1778.

Batch 2 — Networking (3 tests):

  • OCP-28632: Windows and Linux east-west network (uses pre-existing pods in winc-test)
  • OCP-32273: Configure kube proxy and external networking (LoadBalancer)
  • OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

Note: OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch due to its long runtime and disruptive nature.

Planned migration batches (WINC-1778):

Batch Category Tests
1 Node Basics 32554, 32615, 33612
2 (this PR) Networking 28632, 32273, 31276
3 Logging & Monitoring 33779, 33783, 73595
4 WICD & Services 54711, 50403, 56354, 76765, 33794
5 Proxy 65980, 66670, 68320
6 Workloads & Misc 25593, 42204, 48873, 38186, 38188, 60814, 74760

Notes

  • OCP-28632 requires pre-existing win-webserver and linux-webserver pods in the winc-test namespace (provisioned by Flexy/cluster setup)
  • OCP-32273 skips on vsphere, nutanix, and platform=none (no LoadBalancer support)
  • OCP-31276 creates its own namespace and workloads, cleans up on completion

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: weinliu

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 3, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 3, 2026

@weinliu: This pull request references WINC-1778 which is a valid jira issue.

Details

In response to this:

Summary

Migrates the Networking batch of WINC tests as part of WINC-1778.

Batch 2 — Networking (3 tests):

  • OCP-28632: Windows and Linux east-west network (uses pre-existing pods in winc-test)
  • OCP-32273: Configure kube proxy and external networking (LoadBalancer)
  • OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

Note: OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch due to its long runtime and disruptive nature.

Planned migration batches (WINC-1778):

Batch Category Tests
1 Node Basics 32554, 32615, 33612
2 (this PR) Networking 28632, 32273, 31276
3 Logging & Monitoring 33779, 33783, 73595
4 WICD & Services 54711, 50403, 56354, 76765, 33794
5 Proxy 65980, 66670, 68320
6 Workloads & Misc 25593, 42204, 48873, 38186, 38188, 60814, 74760

Notes

  • OCP-28632 requires pre-existing win-webserver and linux-webserver pods in the winc-test namespace (provisioned by Flexy/cluster setup)
  • OCP-32273 skips on vsphere, nutanix, and platform=none (no LoadBalancer support)
  • OCP-31276 creates its own namespace and workloads, cleans up on completion

Summary by CodeRabbit

  • Tests
  • Added new Windows networking test suite covering East-West traffic validation between Windows and Linux workloads
  • Added external networking tests to verify LoadBalancer service functionality
  • Added internal networking tests validating CNI, multi-replica deployments, and cross-node cluster connectivity

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
ote/test/extended/networking.go (1)

252-254: Minor: Error wrapping with potentially nil error.

When out == "" but err == nil, wrapping a nil error with %w produces %!w(<nil>) in the message. This pattern repeats in getPodIPs, getPodHostIPs, and getServiceClusterIP. Not a blocker since the message still conveys the failure, but consider explicitly constructing the error without %w when err is nil for cleaner diagnostics.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ote/test/extended/networking.go` around lines 252 - 254, The error message is
wrapping a possibly nil error with %w (e.g., in the pod lookup code and the
functions getPodIPs, getPodHostIPs, getServiceClusterIP), which renders as
%!w(<nil>); change the return logic to check if err == nil and construct a plain
fmt.Errorf("no pods found for %s in %s", deployment, namespace) (or similar) in
that branch, otherwise return fmt.Errorf("no pods found for %s in %s: %w",
deployment, namespace, err) to preserve the original error when present.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@ote/test/extended/networking.go`:
- Around line 414-418: The comment above the pod exec is inaccurate: the code
calls getPodNames(oc, windowsWorkloads, namespace) and executes
oc.AsAdmin().Run("exec", ... pods[0], "--", "curl" ...) against a Windows pod,
not a Linux pod; update the comment to state that the curl is performed from a
Windows pod (or remove the OS-specific note) so it matches getPodNames,
windowsWorkloads and the oc.AsAdmin().Run exec usage.
- Around line 502-514: The DNS names for the services are hardcoded to the wrong
namespace (windowsServiceDNS, linuxServiceDNS) causing failures in
CheckCNIAndInternalNetworking; replace those constants with dynamic DNS strings
built from the local namespace variable (e.g., construct
"win-webserver.%s.svc.cluster.local" and
"linux-webserver.%s.svc.cluster.local:8080" using namespace) and use those new
winDNS/linuxDNS values in the two Output calls so the curl/pwsh requests target
the deployed namespace rather than the hardcoded winc-test.

---

Nitpick comments:
In `@ote/test/extended/networking.go`:
- Around line 252-254: The error message is wrapping a possibly nil error with
%w (e.g., in the pod lookup code and the functions getPodIPs, getPodHostIPs,
getServiceClusterIP), which renders as %!w(<nil>); change the return logic to
check if err == nil and construct a plain fmt.Errorf("no pods found for %s in
%s", deployment, namespace) (or similar) in that branch, otherwise return
fmt.Errorf("no pods found for %s in %s: %w", deployment, namespace, err) to
preserve the original error when present.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: a70ffb78-fded-4a7c-bb65-b6958be80356

📥 Commits

Reviewing files that changed from the base of the PR and between 13e7a27 and 3c74f63.

📒 Files selected for processing (2)
  • ote/cmd/wmco-tests-ext/main.go
  • ote/test/extended/networking.go

Comment on lines +414 to +418
// Use oc exec from a Linux pod to curl the LB since we may not have direct access
pods, err := getPodNames(oc, windowsWorkloads, namespace)
if err == nil && len(pods) > 0 {
msg, _, _ := oc.AsAdmin().Run("exec", "-n", namespace, pods[0],
"--", "curl", "--max-time", "10", "http://"+endpoint)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Misleading comment: code uses Windows pod, not Linux.

The comment says "Use oc exec from a Linux pod" but pods is fetched from windowsWorkloads - you're curling from the Windows pod. This works fine (Windows can curl its own LB endpoint), but the comment should be corrected to avoid confusion during future maintenance.

📝 Proposed fix
-		// Use oc exec from a Linux pod to curl the LB since we may not have direct access
+		// Use oc exec from a Windows pod to curl the LB since we may not have direct access
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
// Use oc exec from a Linux pod to curl the LB since we may not have direct access
pods, err := getPodNames(oc, windowsWorkloads, namespace)
if err == nil && len(pods) > 0 {
msg, _, _ := oc.AsAdmin().Run("exec", "-n", namespace, pods[0],
"--", "curl", "--max-time", "10", "http://"+endpoint)
// Use oc exec from a Windows pod to curl the LB since we may not have direct access
pods, err := getPodNames(oc, windowsWorkloads, namespace)
if err == nil && len(pods) > 0 {
msg, _, _ := oc.AsAdmin().Run("exec", "-n", namespace, pods[0],
"--", "curl", "--max-time", "10", "http://"+endpoint)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ote/test/extended/networking.go` around lines 414 - 418, The comment above
the pod exec is inaccurate: the code calls getPodNames(oc, windowsWorkloads,
namespace) and executes oc.AsAdmin().Run("exec", ... pods[0], "--", "curl" ...)
against a Windows pod, not a Linux pod; update the comment to state that the
curl is performed from a Windows pod (or remove the OS-specific note) so it
matches getPodNames, windowsWorkloads and the oc.AsAdmin().Run exec usage.

Comment on lines +502 to +514
// Linux → Windows via DNS
msg, err = oc.AsAdmin().Output("exec", "-n", namespace, linuxPods[0],
"--", "curl", windowsServiceDNS)
if err != nil || !strings.Contains(msg, "Windows Container Web Server") {
return fmt.Errorf("Linux pod cannot reach Windows pod via DNS: %s", msg)
}

// Windows → Linux via DNS
msg, err = oc.AsAdmin().Output("exec", "-n", namespace, winPods[0],
"--", "pwsh.exe", "-Command", psInvokeWebRequest("http://"+linuxServiceDNS))
if err != nil || !strings.Contains(msg, "Linux Container Web Server") {
return fmt.Errorf("Windows pod cannot reach Linux pod via DNS: %s", msg)
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify if the constants are used anywhere else that might justify keeping them
rg -n "windowsServiceDNS|linuxServiceDNS" --type go

Repository: openshift/windows-machine-config-operator

Length of output: 477


🏁 Script executed:

# Get the function containing lines 502-514 and see the namespace being used
sed -n '428,527p' ote/test/extended/networking.go | cat -n

Repository: openshift/windows-machine-config-operator

Length of output: 4535


Critical: DNS hardcoding to wrong namespace breaks OCP-31276 test.

The constants windowsServiceDNS and linuxServiceDNS are hardcoded to winc-test, but CheckCNIAndInternalNetworking deploys workloads in winc-31276. DNS queries fail because win-webserver.winc-test.svc.cluster.local doesn't exist—the service is at win-webserver.winc-31276.svc.cluster.local.

Construct DNS names dynamically using the namespace variable:

winDNS := fmt.Sprintf("win-webserver.%s.svc.cluster.local", namespace)
linuxDNS := fmt.Sprintf("linux-webserver.%s.svc.cluster.local:8080", namespace)

These constants are only used here (no other callers), so removing them is safe.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ote/test/extended/networking.go` around lines 502 - 514, The DNS names for
the services are hardcoded to the wrong namespace (windowsServiceDNS,
linuxServiceDNS) causing failures in CheckCNIAndInternalNetworking; replace
those constants with dynamic DNS strings built from the local namespace variable
(e.g., construct "win-webserver.%s.svc.cluster.local" and
"linux-webserver.%s.svc.cluster.local:8080" using namespace) and use those new
winDNS/linuxDNS values in the two Output calls so the curl/pwsh requests target
the deployed namespace rather than the hardcoded winc-test.

@weinliu
Copy link
Copy Markdown
Contributor Author

weinliu commented Apr 3, 2026

/retest lint

@weinliu
Copy link
Copy Markdown
Contributor Author

weinliu commented Apr 3, 2026

/retest security

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

@weinliu: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test aws-e2e-operator
/test azure-e2e-operator
/test azure-e2e-upgrade
/test ci-bundle-wmco-bundle
/test gcp-e2e-operator
/test images
/test lint
/test nutanix-e2e-operator
/test platform-none-vsphere-e2e-operator
/test security
/test unit
/test vsphere-disconnected-e2e-operator
/test vsphere-e2e-operator
/test vsphere-proxy-e2e-operator
/test wicd-unit-vsphere

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-windows-machine-config-operator-master-ci-bundle-wmco-bundle
pull-ci-openshift-windows-machine-config-operator-master-images
pull-ci-openshift-windows-machine-config-operator-master-lint
pull-ci-openshift-windows-machine-config-operator-master-security
pull-ci-openshift-windows-machine-config-operator-master-unit
Details

In response to this:

/retest security

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

@weinliu: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test aws-e2e-operator
/test azure-e2e-operator
/test azure-e2e-upgrade
/test ci-bundle-wmco-bundle
/test gcp-e2e-operator
/test images
/test lint
/test nutanix-e2e-operator
/test platform-none-vsphere-e2e-operator
/test security
/test unit
/test vsphere-disconnected-e2e-operator
/test vsphere-e2e-operator
/test vsphere-proxy-e2e-operator
/test wicd-unit-vsphere

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-windows-machine-config-operator-master-ci-bundle-wmco-bundle
pull-ci-openshift-windows-machine-config-operator-master-images
pull-ci-openshift-windows-machine-config-operator-master-lint
pull-ci-openshift-windows-machine-config-operator-master-security
pull-ci-openshift-windows-machine-config-operator-master-unit
Details

In response to this:

/retest lint

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Migrate the following networking smokerun tests from openshift-tests-private
to the OTE extension binary:

- OCP-28632: Windows and Linux east-west network (uses pre-existing pods)
- OCP-32273: Configure kube proxy and external networking (LoadBalancer)
- OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch
due to its long runtime and disruptive nature ([Slow][Disruptive]).
@weinliu weinliu force-pushed the WINC-1778-ote-batch2-networking branch from 8ffea47 to f6ef066 Compare April 3, 2026 17:28
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

@weinliu: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 3, 2026

@weinliu: This pull request references WINC-1778 which is a valid jira issue.

Details

In response to this:

Summary

Migrates the Networking batch of WINC tests as part of WINC-1778.

Batch 2 — Networking (3 tests):

  • OCP-28632: Windows and Linux east-west network (uses pre-existing pods in winc-test)
  • OCP-32273: Configure kube proxy and external networking (LoadBalancer)
  • OCP-31276: Configure CNI and internal networking (pod-to-pod + DNS)

Note: OCP-39451 (ClusterIP with MachineSet scaling) is excluded from this batch due to its long runtime and disruptive nature.

Planned migration batches (WINC-1778):

Batch Category Tests Status
0 wmco golang version 37362 ✅ merged
1 (PR #3920) Node Basics 32554, 32615, 33612 🔄 in review
2 (PR #3922) Networking 28632, 32273, 31276 🔄 in review
3 (PR #3921) Logging & Monitoring 33779, 33783, 73595 🔄 in review
4 WICD, Workloads & Misc (no SSH) 50403, 60814, 25593, 42204, 38186 📋 planned
5 SSH-dependent tests 54711, 56354, 76765, 48873, 65980, 66670, 68320 ⏳ pending SSH decision
Special Needs special cluster 74760, 38188 ⏳ pending

Notes

  • OCP-28632 requires pre-existing win-webserver and linux-webserver pods in the winc-test namespace (provisioned by Flexy/cluster setup)
  • OCP-32273 skips on vsphere, nutanix, and platform=none (no LoadBalancer support)
  • OCP-31276 creates its own namespace and workloads, cleans up on completion

Summary by CodeRabbit

  • Tests
  • Added new Windows networking test suite covering East-West traffic validation between Windows and Linux workloads
  • Added external networking tests to verify LoadBalancer service functionality
  • Added internal networking tests validating CNI, multi-replica deployments, and cross-node cluster connectivity

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Copy Markdown

Closing, please open a separate request if this work is still required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants