apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60827" uid: f16d620b-7886-43a3-9566-4dadb2b691f7 spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-11T03:52:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.24433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 943.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 1.057249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 1.163467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 1.255963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 935.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:22:33Z" - latency: 1.078708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:21:33Z" - latency: 1.015301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:20:33Z" - latency: 1.107679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:19:33Z" - latency: 927.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:18:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60830" uid: 413d3820-8f2f-479f-92ff-9cfa37baae52 spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T03:51:33Z" message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.590593ms message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 12.82635ms message: 'load-balancer-api-external: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:27:33Z" - latency: 5.476583ms message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 6.115538ms message: 'load-balancer-api-external: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:26:33Z" - latency: 3.552036ms message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 7.263921ms message: 'load-balancer-api-external: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:25:33Z" - latency: 3.614518ms message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 7.759819ms message: 'load-balancer-api-external: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:24:33Z" - latency: 4.005305ms message: 'load-balancer-api-external: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 6.843903ms message: 'load-balancer-api-external: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:23:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60828" uid: 18c8303d-48b4-409b-b817-7e47feef9fed spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T03:51:33Z" message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.088899ms message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 12.702499ms message: 'load-balancer-api-internal: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:27:33Z" - latency: 5.492259ms message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 6.00512ms message: 'load-balancer-api-internal: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:26:33Z" - latency: 3.579277ms message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 7.312267ms message: 'load-balancer-api-internal: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:25:33Z" - latency: 3.66923ms message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 7.634283ms message: 'load-balancer-api-internal: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:24:33Z" - latency: 3.981031ms message: 'load-balancer-api-internal: tcp connection to a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 6.720498ms message: 'load-balancer-api-internal: resolved host name a5d4e4484f86044e5872256bea3fb5e0-3650b62646460ff1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:23:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-138-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60824" uid: 69b717cb-08ff-453b-980a-de000057530a spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:52:33Z" message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.204394ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 2.038151ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 2.379806ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 1.981514ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 2.264963ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 2.148003ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:22:33Z" - latency: 2.425346ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:21:33Z" - latency: 1.981401ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:20:33Z" - latency: 2.046325ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:19:33Z" - latency: 2.018244ms message: 'network-check-target-ip-10-0-138-240: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:18:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-140-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60823" uid: b8d78ca7-8de9-429d-80a6-e8bd2bf527bb spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:52:33Z" message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.400319ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 846.64µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 905.912µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 901.308µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 877.509µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 1.187033ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:22:33Z" - latency: 897.648µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:21:33Z" - latency: 1.108495ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:20:33Z" - latency: 911.6µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:19:33Z" - latency: 972.54µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:18:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-142-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60825" uid: 802e98b5-db5a-4d86-b20c-2262fc4d2d7d spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:52:33Z" message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.130979ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 2.292342ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 2.391453ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 2.134413ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 2.473338ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 2.198827ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:22:33Z" - latency: 2.08151ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:21:33Z" - latency: 2.206744ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:20:33Z" - latency: 2.136581ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:19:33Z" - latency: 2.227866ms message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:18:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:45:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 8332d2d7-88df-46ca-8156-c87a3da6ed23 resourceVersion: "60826" uid: cfd5c287-7020-4e52-9bff-4687dc5b2750 spec: sourcePod: network-check-source-869dcfcdcd-p8hsg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-11T03:51:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.121µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:33Z" - latency: 1.807492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:27:33Z" - latency: 941.911µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:33Z" - latency: 1.745309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:26:33Z" - latency: 786.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:33Z" - latency: 2.603303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:25:33Z" - latency: 914.083µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:33Z" - latency: 1.775727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:24:33Z" - latency: 1.184365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:23:33Z" - latency: 1.584306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:23:33Z" kind: List metadata: resourceVersion: ""