{"id":"networking-and-observability-integrated-stack","text":"OpenShift networking and network observability form an integrated stack: the layered CNI architecture (OVN-Kubernetes + Multus) with dual-stack addressing provides the data plane, while the observability pipeline (eBPF→FlowCollector→Loki) provides flow-level visibility — both following the platform's explicit multi-component enablement pattern.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["complete-networking-discovery-data-and-addressing","observability-follows-platform-enablement-pattern"],"outlist":[],"label":"Networking and network observability are architecturally coupled — observability consumes the CNI stack it monitors, and both require explicit enablement beyond defaults."}],"dependents":["runtime-operations-fully-observable-within-governance","runtime-operations-require-integrated-networking-and-resource-governance"],"metadata":{},"explanation":{"steps":[{"node":"networking-and-observability-integrated-stack","truth_value":"IN","reason":"SL justification valid","antecedents":["complete-networking-discovery-data-and-addressing","observability-follows-platform-enablement-pattern"],"label":"Networking and network observability are architecturally coupled — observability consumes the CNI stack it monitors, and both require explicit enablement beyond defaults."},{"node":"complete-networking-discovery-data-and-addressing","truth_value":"IN","reason":"SL justification valid","antecedents":["cluster-networking-spans-discovery-and-data-plane","network-architecture-layered-with-dual-stack-constraints"],"label":"Both depth-2 nodes share multi-CNI architecture as foundation but capture orthogonal concerns (discovery+data vs addressing+constraints); combining reveals that addressing constraints propagate back to restrict data plane options"},{"node":"cluster-networking-spans-discovery-and-data-plane","truth_value":"IN","reason":"SL justification valid","antecedents":["dns-service-discovery-architecture","multi-cni-network-architecture"],"label":"depth-2 — discovery and data plane are independently architected but jointly required for connectivity"},{"node":"dns-service-discovery-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["dns-operator-deploys-coredns-daemonset","dns-cluster-ip-10th-address-service-cidr","dns-cluster-local-invalid-forwarding-zone","ocp-dns-naming-convention"],"label":"DNS architecture is fully deterministic from the service CIDR — the IP, naming, and forwarding constraints form a closed system"},{"node":"dns-operator-deploys-coredns-daemonset","truth_value":"IN","reason":"premise"},{"node":"dns-cluster-ip-10th-address-service-cidr","truth_value":"IN","reason":"premise"},{"node":"dns-cluster-local-invalid-forwarding-zone","truth_value":"IN","reason":"premise"},{"node":"ocp-dns-naming-convention","truth_value":"IN","reason":"premise"},{"node":"multi-cni-network-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-default-cni-shifted-to-ovn-kubernetes","ocp-multus-cni-multiple-interfaces","multus-cni-enables-multiple-network-attachments","pods-reference-nads-via-annotation"],"label":"Primary + meta-plugin + secondary plugin layering defines the network model"},{"node":"ocp-default-cni-shifted-to-ovn-kubernetes","truth_value":"IN","reason":"premise"},{"node":"ocp-multus-cni-multiple-interfaces","truth_value":"IN","reason":"premise"},{"node":"multus-cni-enables-multiple-network-attachments","truth_value":"IN","reason":"premise"},{"node":"pods-reference-nads-via-annotation","truth_value":"IN","reason":"premise"},{"node":"network-architecture-layered-with-dual-stack-constraints","truth_value":"IN","reason":"SL justification valid","antecedents":["multi-cni-network-architecture","dual-stack-networking-with-constraints"],"label":"The CNI layering model and dual-stack addressing are orthogonal features that interact at constraint boundaries"},{"node":"multi-cni-network-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-default-cni-shifted-to-ovn-kubernetes","ocp-multus-cni-multiple-interfaces","multus-cni-enables-multiple-network-attachments","pods-reference-nads-via-annotation"],"label":"Primary + meta-plugin + secondary plugin layering defines the network model"},{"node":"ocp-default-cni-shifted-to-ovn-kubernetes","truth_value":"IN","reason":"premise"},{"node":"ocp-multus-cni-multiple-interfaces","truth_value":"IN","reason":"premise"},{"node":"multus-cni-enables-multiple-network-attachments","truth_value":"IN","reason":"premise"},{"node":"pods-reference-nads-via-annotation","truth_value":"IN","reason":"premise"},{"node":"dual-stack-networking-with-constraints","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-supports-dual-stack-ipv4-ipv6","ovn-kubernetes-single-service-network-block","udn-default-mtu-1400","ocp-virt-no-single-stack-ipv6"],"label":"Dual-stack support exists but with per-component constraints"},{"node":"ocp-supports-dual-stack-ipv4-ipv6","truth_value":"IN","reason":"premise"},{"node":"ovn-kubernetes-single-service-network-block","truth_value":"IN","reason":"premise"},{"node":"udn-default-mtu-1400","truth_value":"IN","reason":"premise"},{"node":"ocp-virt-no-single-stack-ipv6","truth_value":"IN","reason":"premise"},{"node":"observability-follows-platform-enablement-pattern","truth_value":"IN","reason":"SL justification valid","antecedents":["observability-requires-layered-enablement","explicit-multi-component-enablement-pattern"],"label":"depth-2 observability enablement + depth-2 multi-component pattern reveal observability as an instance of a platform-wide architectural pattern"},{"node":"observability-requires-layered-enablement","truth_value":"IN","reason":"SL justification valid","antecedents":["monitoring-stack-layered-architecture","monitoring-requires-explicit-enablement-beyond-platform"],"label":"Architecture is layered AND enablement is layered — two independent dimensions that compound operational complexity"},{"node":"monitoring-stack-layered-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-alertingrule-generates-prometheusrule","ocp-alertrelabelconfig-before-alertmanager","ocp-inhibit-rules-source-target-matching"],"label":"Three sequential processing stages form a coherent alert pipeline from rule firing to delivery"},{"node":"ocp-alertingrule-generates-prometheusrule","truth_value":"IN","reason":"premise"},{"node":"ocp-alertrelabelconfig-before-alertmanager","truth_value":"IN","reason":"premise"},{"node":"ocp-inhibit-rules-source-target-matching","truth_value":"IN","reason":"premise"},{"node":"monitoring-requires-explicit-enablement-beyond-platform","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-cluster-monitoring-default-user-workload-explicit","user-defined-monitoring-not-default","distributed-tracing-not-enabled-by-default"],"label":"Consistent pattern of opt-in for non-platform observability features"},{"node":"ocp-cluster-monitoring-default-user-workload-explicit","truth_value":"IN","reason":"premise"},{"node":"user-defined-monitoring-not-default","truth_value":"IN","reason":"premise"},{"node":"distributed-tracing-not-enabled-by-default","truth_value":"IN","reason":"premise"},{"node":"explicit-multi-component-enablement-pattern","truth_value":"IN","reason":"SL justification valid","antecedents":["service-mesh-multi-operator-architecture","monitoring-requires-explicit-enablement-beyond-platform"],"label":"depth-2 — both mesh and advanced observability share the explicit-enablement-beyond-defaults pattern"},{"node":"service-mesh-multi-operator-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["service-mesh-requires-multiple-operators","service-mesh-multi-tenant-default","service-mesh-3x-based-on-istio-sail","serverless-integrates-with-service-mesh"],"label":"Service Mesh architectural properties combine into a distinct multi-operator multi-tenant model"},{"node":"service-mesh-requires-multiple-operators","truth_value":"IN","reason":"premise"},{"node":"service-mesh-multi-tenant-default","truth_value":"IN","reason":"premise"},{"node":"service-mesh-3x-based-on-istio-sail","truth_value":"IN","reason":"premise"},{"node":"serverless-integrates-with-service-mesh","truth_value":"IN","reason":"premise"},{"node":"monitoring-requires-explicit-enablement-beyond-platform","truth_value":"IN","reason":"SL justification valid","antecedents":["ocp-cluster-monitoring-default-user-workload-explicit","user-defined-monitoring-not-default","distributed-tracing-not-enabled-by-default"],"label":"Consistent pattern of opt-in for non-platform observability features"},{"node":"ocp-cluster-monitoring-default-user-workload-explicit","truth_value":"IN","reason":"premise"},{"node":"user-defined-monitoring-not-default","truth_value":"IN","reason":"premise"},{"node":"distributed-tracing-not-enabled-by-default","truth_value":"IN","reason":"premise"}]}}