apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64669" uid: 4f4c5efc-e303-4a5e-9abc-64dc2e3aa9e3 spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T20:15:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 884.375µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 930.659µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 1.004355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 989.481µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 1.066326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:45:14Z" - latency: 859.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:44:14Z" - latency: 1.076442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:43:14Z" - latency: 1.059787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:42:14Z" - latency: 911.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64671" uid: 9afac06d-20b1-4857-a550-f30bc7e5024d spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T20:14:14Z" message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.100091ms message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 9.661758ms message: 'load-balancer-api-external: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:50:14Z" - latency: 5.216963ms message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 10.207589ms message: 'load-balancer-api-external: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:49:14Z" - latency: 5.075393ms message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 8.769138ms message: 'load-balancer-api-external: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:48:14Z" - latency: 5.994119ms message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 6.697109ms message: 'load-balancer-api-external: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:47:14Z" - latency: 4.021824ms message: 'load-balancer-api-external: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 9.101322ms message: 'load-balancer-api-external: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64670" uid: 7d4a3651-b625-480f-9fcf-0f205724aaf3 spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T20:14:14Z" message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.119101ms message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 9.548119ms message: 'load-balancer-api-internal: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:50:14Z" - latency: 5.243038ms message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 10.103534ms message: 'load-balancer-api-internal: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:49:14Z" - latency: 4.788781ms message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 8.662791ms message: 'load-balancer-api-internal: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:48:14Z" - latency: 6.036901ms message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 6.640576ms message: 'load-balancer-api-internal: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:47:14Z" - latency: 5.212636ms message: 'load-balancer-api-internal: tcp connection to abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 9.057599ms message: 'load-balancer-api-internal: resolved host name abf174a0519444f5eafa223e8e08cf21-7e4f2329f876a909.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T20:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-133-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64665" uid: ca62e650-f384-424a-a6d5-a63e2a1e4e3f spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T20:15:14Z" message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.418µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 923.047µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 1.203889ms message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 983.42µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 1.395583ms message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 913.107µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:45:14Z" - latency: 1.036623ms message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:44:14Z" - latency: 971.723µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:43:14Z" - latency: 936.679µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:42:14Z" - latency: 817.941µs message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-139-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64666" uid: cf6b9c4e-5890-40f4-be00-50fc1464fd3f spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T20:15:14Z" message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.367794ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 2.517009ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 2.292984ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 2.495945ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 2.472394ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 2.520746ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:45:14Z" - latency: 2.662574ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:44:14Z" - latency: 2.300733ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:43:14Z" - latency: 2.614741ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:42:14Z" - latency: 2.757864ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-143-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64667" uid: bf99a56b-7494-4579-9a0f-e4e5618edf89 spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T20:15:14Z" message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.116512ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 2.411972ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 2.70134ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 2.468349ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 2.263957ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 2.334374ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:45:14Z" - latency: 2.214103ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:44:14Z" - latency: 2.343069ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:43:14Z" - latency: 2.302743ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:42:14Z" - latency: 2.399622ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T20:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-202.ec2.internal uid: 07e3686c-37ee-4955-8029-48fd35ee3aeb resourceVersion: "64668" uid: 4b652084-10b5-4f80-9d18-61cbc6ce2cf7 spec: sourcePod: network-check-source-7bc5b6bf85-649wg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T20:14:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.535969ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:50:14Z" - latency: 1.904408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T20:50:14Z" - latency: 927.321µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:49:14Z" - latency: 1.77531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T20:49:14Z" - latency: 967.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:48:14Z" - latency: 1.970952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T20:48:14Z" - latency: 957.815µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:47:14Z" - latency: 1.753756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T20:47:14Z" - latency: 1.042415ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T20:46:14Z" - latency: 2.161731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T20:46:14Z" kind: List metadata: resourceVersion: ""