XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • CNV Network
    • cnv-udn-checkup
    • Hide
      • (Must have) checkup validates Layer 3 UDN configurations within defined namespaces.
      • (Must have) No IP conflicts or network misconfigurations are detected, even with overlapping IPs across namespaces.
      • (Should have) Tests confirm proper traffic isolation between different L3 UDN.
      • All testing is scoped within cluster networking.
      Show
      (Must have) checkup validates Layer 3 UDN configurations within defined namespaces. (Must have) No IP conflicts or network misconfigurations are detected, even with overlapping IPs across namespaces. (Should have) Tests confirm proper traffic isolation between different L3 UDN. All testing is scoped within cluster networking.
    • To Do

      Goal

      Validation for Layer 3 UDN functionality within Kiagnose, focusing solely on intra-cluster networking. The testing will be executed as part of a new checkup, specifically from namespaces where UDN is defined. This validation aims to ensure proper configuration and network isolation of Layer 3 UDNs without involving ingress or egress testing at this stage.

      objectives

      • Extend Kiagnose to validate the configuration and functionality of Layer 3 UDNs within cluster networking.
      • Ensure network isolation and proper routing within namespaces using UDNs.
      • Validate overlapping IP address ranges across namespaces, ensuring correct IP management without conflicts.

      User Stories

      • As a user, I want Kiagnose to validate the configuration of my Layer 3 UDN within my namespace and ensure no misconfigurations or IP conflicts are present.
      • As a network administrator, I want Kiagnose to verify that pods within different Layer 3 UDNs in separate namespaces are isolated, ensuring no network traffic leakage.
      • As a user, I want to ensure that overlapping IP address spaces across different namespaces using Layer 3 UDNs are handled correctly, with Kiagnose providing diagnostics for any issues.

      Non-Requirements

      • Ingress/egress traffic and any external network connectivity testing.
      • Validation for Layer 2 UDNs or other network types beyond Layer 3.

      Notes

      • <...>

              Unassigned Unassigned
              nrozen@redhat.com Nir Rozen
              Yossi Segev Yossi Segev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: