apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32449" uid: 12d38a15-9486-40ee-8865-576668712d5a spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T10:19:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.106591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 1.053529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 1.405314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 1.03571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 1.295414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 1.033411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:49:23Z" - latency: 1.081083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:48:23Z" - latency: 1.011774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:47:23Z" - latency: 1.103676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:46:23Z" - latency: 1.073795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32451" uid: 86ba15c2-4994-4273-82a7-b890f4a98497 spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:23Z" message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.542755ms message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 8.740446ms message: 'load-balancer-api-external: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:54:23Z" - latency: 4.562826ms message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 9.228395ms message: 'load-balancer-api-external: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:53:23Z" - latency: 4.182666ms message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 8.403658ms message: 'load-balancer-api-external: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:52:23Z" - latency: 6.080387ms message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 11.226864ms message: 'load-balancer-api-external: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:51:23Z" - latency: 5.535043ms message: 'load-balancer-api-external: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 8.800038ms message: 'load-balancer-api-external: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32450" uid: 26b1b832-d000-4475-a543-286f620be487 spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:23Z" message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.525216ms message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 8.636382ms message: 'load-balancer-api-internal: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:54:23Z" - latency: 4.876037ms message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 9.294403ms message: 'load-balancer-api-internal: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:53:23Z" - latency: 4.966222ms message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 8.38425ms message: 'load-balancer-api-internal: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:52:23Z" - latency: 4.048699ms message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 11.179952ms message: 'load-balancer-api-internal: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:51:23Z" - latency: 5.573977ms message: 'load-balancer-api-internal: tcp connection to a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 8.719068ms message: 'load-balancer-api-internal: resolved host name a15fb23b1393e40858197558dd384185-550d58f9a425e0f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-network-check-target-ip-10-0-130-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32446" uid: 31147c43-96d6-40a0-9cf7-e4464e5eb583 spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:23Z" message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222424ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 2.512053ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 2.522888ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 2.039191ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 2.339323ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 2.137507ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:49:23Z" - latency: 2.24005ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:48:23Z" - latency: 2.137966ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:47:23Z" - latency: 2.236415ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:46:23Z" - latency: 1.986442ms message: 'network-check-target-ip-10-0-130-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-network-check-target-ip-10-0-131-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32448" uid: 1bdb769d-5f0a-4e48-bda2-bb63661d3f8e spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:23Z" message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.242176ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 2.255839ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 2.329954ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 2.325766ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 2.927528ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 2.278834ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:49:23Z" - latency: 2.190322ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:48:23Z" - latency: 2.126815ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:47:23Z" - latency: 2.371042ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:46:23Z" - latency: 2.369998ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-network-check-target-ip-10-0-140-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32445" uid: 835a8df8-1693-475a-b9da-028f401d96d4 spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:23Z" message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.293µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 908.037µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 928.194µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 917.729µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 1.508591ms message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 1.23969ms message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:49:23Z" - latency: 900.139µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:48:23Z" - latency: 941.762µs message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:47:23Z" - latency: 1.282965ms message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:46:23Z" - latency: 1.179686ms message: 'network-check-target-ip-10-0-140-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-175.ec2.internal uid: c88c0088-b97a-461b-a9a8-1dbe188ea709 resourceVersion: "32447" uid: df2574e1-dbd1-45fc-93d4-76e8b5c81b44 spec: sourcePod: network-check-source-7d88cb55d8-29c9r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T10:18:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.207086ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:54:23Z" - latency: 1.99404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:54:23Z" - latency: 900.461µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:53:23Z" - latency: 1.712151ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:53:23Z" - latency: 1.198878ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:52:23Z" - latency: 1.981762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:52:23Z" - latency: 1.038751ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:51:23Z" - latency: 1.92432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:51:23Z" - latency: 981.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:50:23Z" - latency: 1.926659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:50:23Z" kind: List metadata: resourceVersion: ""