apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62823" uid: f0989d1b-b355-498e-b635-f3a3a2bd731b spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T02:31:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.063555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 906.7µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 924.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 1.08479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 973.422µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 937.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:20Z" - latency: 1.327213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:20Z" - latency: 833.335µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:20Z" - latency: 905.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:20Z" - latency: 1.215441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62824" uid: 7e350965-ccf7-4fc0-a22c-f3cb926d40a5 spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:30:20Z" message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.286893ms message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 7.411617ms message: 'load-balancer-api-external: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:06:20Z" - latency: 4.002646ms message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 8.243053ms message: 'load-balancer-api-external: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:20Z" - latency: 5.463163ms message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 8.919228ms message: 'load-balancer-api-external: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:20Z" - latency: 4.937046ms message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 8.078208ms message: 'load-balancer-api-external: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:20Z" - latency: 3.660391ms message: 'load-balancer-api-external: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 8.485804ms message: 'load-balancer-api-external: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62825" uid: 3d201abc-0d7c-4a7d-96b8-960d947760d2 spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:30:20Z" message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.3615ms message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 7.474739ms message: 'load-balancer-api-internal: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:06:20Z" - latency: 4.030304ms message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 8.172592ms message: 'load-balancer-api-internal: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:20Z" - latency: 3.770014ms message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 8.958392ms message: 'load-balancer-api-internal: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:20Z" - latency: 4.936638ms message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 8.152357ms message: 'load-balancer-api-internal: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:20Z" - latency: 3.638746ms message: 'load-balancer-api-internal: tcp connection to a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 8.521633ms message: 'load-balancer-api-internal: resolved host name a74d3d708b4a7405da46a793decd6345-7600f10c0ff23126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-134-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62819" uid: 3618a886-63c1-49fe-82a1-d8c879307290 spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:31:20Z" message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.622µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 877.644µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 828.856µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 889.143µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 985.618µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 876.079µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:20Z" - latency: 1.076981ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:20Z" - latency: 1.17227ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:20Z" - latency: 826.164µs message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:20Z" - latency: 1.365932ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-137-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62820" uid: 7fca03a0-6b7c-405a-882f-dab55b401678 spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:31:20Z" message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.26788ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 2.380907ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 2.314472ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 2.36649ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 2.118586ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 2.045401ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:20Z" - latency: 2.409491ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:20Z" - latency: 2.231197ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:20Z" - latency: 2.313638ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:20Z" - latency: 2.353517ms message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-140-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62821" uid: 9c6e3fb7-d90a-47a7-b024-f157761fb14d spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:31:20Z" message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.407423ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 2.346635ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 2.430869ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 2.379511ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 2.343086ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 2.525554ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:20Z" - latency: 2.57678ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:20Z" - latency: 2.440843ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:20Z" - latency: 1.821449ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:20Z" - latency: 2.33587ms message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:24:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-165-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-165.ec2.internal uid: f69f76b3-0eb4-4ef7-9bc3-253fb80aaf00 resourceVersion: "62822" uid: 70a17605-ec97-41b5-bcdd-2b3e973dcde9 spec: sourcePod: network-check-source-7bc5b6bf85-x7dbj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T02:30:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:20Z" - latency: 2.033512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:06:20Z" - latency: 968.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:20Z" - latency: 1.867972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:20Z" - latency: 866.184µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:20Z" - latency: 2.100525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:20Z" - latency: 891.204µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:20Z" - latency: 2.053129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:20Z" - latency: 1.440334ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:20Z" - latency: 1.711716ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:20Z" kind: List metadata: resourceVersion: ""