apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "30760" uid: 3f7626f7-71d8-4c12-97a5-f8d10eeb3e2e spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:00:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.340354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:35Z" - latency: 1.240449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:35Z" - latency: 1.270031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 1.422418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 1.367519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 1.155585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 974.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 881.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:00:35Z" - latency: 981.095µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:59:35Z" - latency: 1.701368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:58:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "25850" uid: 69ba7b30-3859-45b8-aca2-50c0b0bc3033 spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:59:35Z" message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.579178ms message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 8.667745ms message: 'load-balancer-api-external: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:05:35Z" - latency: 5.299274ms message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 6.941372ms message: 'load-balancer-api-external: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:04:35Z" - latency: 5.801937ms message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 6.98875ms message: 'load-balancer-api-external: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:03:35Z" - latency: 5.659442ms message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 6.927818ms message: 'load-balancer-api-external: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:02:35Z" - latency: 5.555205ms message: 'load-balancer-api-external: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 6.745054ms message: 'load-balancer-api-external: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:01:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "25849" uid: ad6bc623-b3b2-4fcd-bbcb-9b000091edcf spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:59:35Z" message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.535615ms message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 8.758057ms message: 'load-balancer-api-internal: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:05:35Z" - latency: 5.711434ms message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 7.01829ms message: 'load-balancer-api-internal: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:04:35Z" - latency: 5.801802ms message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 7.104271ms message: 'load-balancer-api-internal: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:03:35Z" - latency: 6.145343ms message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 6.979181ms message: 'load-balancer-api-internal: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:02:35Z" - latency: 5.652005ms message: 'load-balancer-api-internal: tcp connection to a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 6.841845ms message: 'load-balancer-api-internal: resolved host name a300589643e4b424e918c086912f9ba3-7726e68e5de6fad4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:01:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-128-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "30759" uid: c79a7b01-ea25-4f46-89cb-715fd6c31515 spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:35Z" message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.536613ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:35Z" - latency: 2.608455ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:35Z" - latency: 2.725295ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 2.390116ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 2.746438ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 2.33665ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 2.437782ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 1.981188ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:00:35Z" - latency: 2.175111ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:59:35Z" - latency: 2.29406ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:58:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-130-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "30757" uid: 2815977d-9229-44dc-8e46-680a95d1abb7 spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:35Z" message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.345µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:35Z" - latency: 920.254µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:35Z" - latency: 990.655µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 877.756µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 1.547353ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 926.373µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 892.287µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 977.743µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:00:35Z" - latency: 1.784905ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:59:35Z" - latency: 1.116437ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:58:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-135-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "30758" uid: ae47f8be-a70a-47a2-838d-f1147f0f429d spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:35Z" message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.137884ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:35Z" - latency: 2.24427ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:35Z" - latency: 1.95746ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 2.001109ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 2.198828ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 2.116771ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 1.88127ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 1.84981ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:00:35Z" - latency: 1.942769ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:59:35Z" - latency: 1.89633ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:58:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.us-east-2.compute.internal uid: 0f05e0ec-965c-42e6-858c-7d381a509715 resourceVersion: "25848" uid: 568ce855-eb92-4452-8129-9d15ace0fa15 spec: sourcePod: network-check-source-6f78d59f99-jv425 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T19:59:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.29749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:35Z" - latency: 1.589515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:05:35Z" - latency: 802.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:04:35Z" - latency: 1.744067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:04:35Z" - latency: 922.699µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:03:35Z" - latency: 1.742576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:03:35Z" - latency: 1.005028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:02:35Z" - latency: 1.878066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:02:35Z" - latency: 1.035404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:01:35Z" - latency: 1.811824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:01:35Z" kind: List metadata: resourceVersion: ""