apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63397" uid: f19cb97e-c2cd-4af2-b039-9cfdd7af5e6e spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T21:11:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 1.033517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 1.043676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 947.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 886.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 832.665µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:41:22Z" - latency: 1.08497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:40:22Z" - latency: 1.419322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:39:22Z" - latency: 1.166852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:38:22Z" - latency: 867.186µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:37:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63398" uid: f78e7c57-6ac7-4dd1-bdf4-850c394c97fb spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T21:10:22Z" message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.157327ms message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 6.565826ms message: 'load-balancer-api-external: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:46:22Z" - latency: 4.166648ms message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 7.524037ms message: 'load-balancer-api-external: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:45:22Z" - latency: 3.655909ms message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 7.098093ms message: 'load-balancer-api-external: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:44:22Z" - latency: 3.375641ms message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 8.81908ms message: 'load-balancer-api-external: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:43:22Z" - latency: 4.343026ms message: 'load-balancer-api-external: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 6.228625ms message: 'load-balancer-api-external: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63399" uid: d11dbe8a-179b-467b-bbd6-e4b5063c547d spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T21:10:22Z" message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.175965ms message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 6.529068ms message: 'load-balancer-api-internal: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:46:22Z" - latency: 4.180634ms message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 7.488674ms message: 'load-balancer-api-internal: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:45:22Z" - latency: 4.179548ms message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 7.022964ms message: 'load-balancer-api-internal: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:44:22Z" - latency: 3.759596ms message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 8.793452ms message: 'load-balancer-api-internal: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:43:22Z" - latency: 4.336363ms message: 'load-balancer-api-internal: tcp connection to a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 6.183842ms message: 'load-balancer-api-internal: resolved host name a740d6c0f87d74616bc89a188b19a916-c04056f1be6c726f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T21:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-130-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63396" uid: 8ae369e2-b5a0-439e-b366-d726bf9a347b spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:11:22Z" message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.248745ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 2.106535ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 2.403604ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 2.423804ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 2.179489ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 2.137741ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:41:22Z" - latency: 2.22949ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:40:22Z" - latency: 2.607346ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:39:22Z" - latency: 2.312618ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:38:22Z" - latency: 1.750529ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:37:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-132-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63395" uid: ba144b6b-4ba6-4b7a-bc0d-80efe853f25c spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:11:22Z" message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145262ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 1.248489ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 1.492393ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 1.105236ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 1.153542ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 1.089966ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:41:22Z" - latency: 867.609µs message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:40:22Z" - latency: 1.012513ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:39:22Z" - latency: 828.139µs message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:38:22Z" - latency: 1.102ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:37:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-140-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63393" uid: 92dc2100-169d-4f3d-aa0d-904dc0cec25e spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:11:22Z" message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.309351ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 2.366781ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 2.301971ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 2.214794ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 2.164316ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 2.207761ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:41:22Z" - latency: 2.138794ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:40:22Z" - latency: 2.081096ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:39:22Z" - latency: 2.363185ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:38:22Z" - latency: 1.741971ms message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:37:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:04:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-65-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-65.ec2.internal uid: 0f1c8a79-0f17-4563-bfcd-37085f798b59 resourceVersion: "63394" uid: e4a11818-9dc6-4b48-b8d8-ddbe2ea224d4 spec: sourcePod: network-check-source-7bc5b6bf85-q9zsg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T21:10:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:46:22Z" - latency: 1.888631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T21:46:22Z" - latency: 1.12234ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:45:22Z" - latency: 2.0613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T21:45:22Z" - latency: 1.099554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:44:22Z" - latency: 1.934038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T21:44:22Z" - latency: 1.061283ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:43:22Z" - latency: 2.116458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T21:43:22Z" - latency: 1.184782ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T21:42:22Z" - latency: 1.784574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T21:42:22Z" kind: List metadata: resourceVersion: ""