apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "33377" uid: 07b0214c-6dfb-4a8c-b65b-0def1e127704 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-03-18T16:55:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:44:57Z" - latency: 1.356671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:43:57Z" - latency: 980.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 892.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 1.081716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 817.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 898.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 1.037474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:37:57Z" - latency: 1.27408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:36:57Z" - latency: 956.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "32652" uid: 3950b8f3-cd93-40b4-b60b-e1d4ecdebf86 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-03-18T16:54:57Z" message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.418967ms message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 7.664409ms message: 'load-balancer-api-external: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:42:57Z" - latency: 2.860925ms message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 8.394462ms message: 'load-balancer-api-external: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:41:57Z" - latency: 4.951649ms message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 6.631379ms message: 'load-balancer-api-external: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:40:57Z" - latency: 4.427186ms message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 7.832082ms message: 'load-balancer-api-external: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:39:57Z" - latency: 5.001604ms message: 'load-balancer-api-external: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 8.075056ms message: 'load-balancer-api-external: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:38:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "32653" uid: e6e1ef34-af52-46a0-b74f-5ca910822948 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-03-18T16:54:57Z" message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.387999ms message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 7.759607ms message: 'load-balancer-api-internal: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:42:57Z" - latency: 3.175106ms message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 8.323217ms message: 'load-balancer-api-internal: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:41:57Z" - latency: 5.172966ms message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 6.570871ms message: 'load-balancer-api-internal: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:40:57Z" - latency: 4.441775ms message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 7.766481ms message: 'load-balancer-api-internal: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:39:57Z" - latency: 5.0317ms message: 'load-balancer-api-internal: tcp connection to ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 8.150384ms message: 'load-balancer-api-internal: resolved host name ac747f4180773430bb650fa0d6d2d866-9ebdb1f8131deae1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-03-18T17:38:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-network-check-target-ip-10-0-129-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "33374" uid: febfd522-d6c8-4169-bacc-f8ef13906f57 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-18T16:55:57Z" message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.223µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:44:57Z" - latency: 919.024µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:43:57Z" - latency: 1.15928ms message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 1.233256ms message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 846.199µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 1.278405ms message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 937.902µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 886.559µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:37:57Z" - latency: 1.325889ms message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:36:57Z" - latency: 753.179µs message: 'network-check-target-ip-10-0-129-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-network-check-target-ip-10-0-137-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "33375" uid: 62c0be01-ec5b-4475-aeb3-f99055e5b278 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-18T16:55:57Z" message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.615014ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:44:57Z" - latency: 2.174118ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:43:57Z" - latency: 2.148291ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 2.422559ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 2.102133ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 2.204075ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 2.146185ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 2.553025ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:37:57Z" - latency: 2.160267ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:36:57Z" - latency: 2.184376ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-network-check-target-ip-10-0-139-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "33376" uid: 58ed14ea-8540-465a-b8ae-0d6fcff2be5c spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-18T16:55:57Z" message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.545979ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:44:57Z" - latency: 1.800713ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:43:57Z" - latency: 1.968124ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 1.883152ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 2.072857ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 1.802925ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 1.946567ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 1.903453ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:37:57Z" - latency: 2.106329ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:36:57Z" - latency: 2.124717ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T16:48:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-201.ec2.internal uid: 877e395a-3d0e-4e58-bed2-3718aa25a250 resourceVersion: "32651" uid: 45124185-b30b-42b4-9608-5d940b596741 spec: sourcePod: network-check-source-cc88fdd44-km9x2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-18T16:54:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.345µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:42:57Z" - latency: 1.717483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T17:42:57Z" - latency: 736.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:41:57Z" - latency: 1.770305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T17:41:57Z" - latency: 1.266534ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:40:57Z" - latency: 1.838906ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T17:40:57Z" - latency: 778.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:39:57Z" - latency: 1.669597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T17:39:57Z" - latency: 936.025µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T17:38:57Z" - latency: 2.011587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T17:38:57Z" kind: List metadata: resourceVersion: ""