apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54963" uid: 57152da1-f965-4fa2-b4bc-cf4b5816a117 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T09:50:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.468µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 847.023µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 1.004296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 918.909µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 809.172µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 806.935µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:20:29Z" - latency: 904.794µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:19:29Z" - latency: 1.168596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:18:29Z" - latency: 815.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:17:29Z" - latency: 845.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:16:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54964" uid: b0f89534-5cbc-498e-b364-448545915a21 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T09:49:29Z" message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.922777ms message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 8.01149ms message: 'load-balancer-api-external: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:25:29Z" - latency: 4.435432ms message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 7.713832ms message: 'load-balancer-api-external: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:24:29Z" - latency: 6.313708ms message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 9.02253ms message: 'load-balancer-api-external: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:23:29Z" - latency: 4.577626ms message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 8.375021ms message: 'load-balancer-api-external: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:22:29Z" - latency: 5.052905ms message: 'load-balancer-api-external: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 9.243666ms message: 'load-balancer-api-external: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:21:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54965" uid: d44360e2-7792-4b2a-a83e-7808122bf8b9 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T09:49:29Z" message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.81401ms message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 8.108445ms message: 'load-balancer-api-internal: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:25:29Z" - latency: 4.732737ms message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 7.759637ms message: 'load-balancer-api-internal: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:24:29Z" - latency: 3.728745ms message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 9.04931ms message: 'load-balancer-api-internal: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:23:29Z" - latency: 4.659208ms message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 8.271224ms message: 'load-balancer-api-internal: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:22:29Z" - latency: 4.934594ms message: 'load-balancer-api-internal: tcp connection to a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 9.198484ms message: 'load-balancer-api-internal: resolved host name a0c8c2046dd18469385f4544271b7749-6a4b9c6a7efa16c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:21:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-129-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54960" uid: 4328af81-f2a0-4511-aa01-c77a694d1320 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:50:29Z" message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.734734ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 2.226848ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 2.226899ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 3.054778ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 3.291244ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 2.681426ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:20:29Z" - latency: 2.645473ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:19:29Z" - latency: 2.608501ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:18:29Z" - latency: 2.250284ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:17:29Z" - latency: 2.217696ms message: 'network-check-target-ip-10-0-129-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:16:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-135-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54962" uid: ce440ff8-2005-437a-903a-0f756c0c5295 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:50:29Z" message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.268025ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 1.8757ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 2.048452ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 2.210271ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 2.222857ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 1.772745ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:20:29Z" - latency: 1.733844ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:19:29Z" - latency: 2.205616ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:18:29Z" - latency: 2.173925ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:17:29Z" - latency: 1.860568ms message: 'network-check-target-ip-10-0-135-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:16:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-143-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54959" uid: c202a3c9-7f9f-4ec9-ba75-1f9965fd483e spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:50:29Z" message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.770331ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 1.213518ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 856.168µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 866.038µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 779.006µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 918.748µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:20:29Z" - latency: 673.299µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:19:29Z" - latency: 955.832µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:18:29Z" - latency: 743.528µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:17:29Z" - latency: 721.152µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:16:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:43:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 141918b3-c678-4022-914b-9c37d42b7131 resourceVersion: "54961" uid: f87daba1-daa5-4dbf-8186-5146b7fde878 spec: sourcePod: network-check-source-65bdbbff45-6lfct targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T09:49:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.973µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:25:29Z" - latency: 2.03825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:25:29Z" - latency: 803.216µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:24:29Z" - latency: 1.933314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:24:29Z" - latency: 960.261µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:23:29Z" - latency: 1.641564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:23:29Z" - latency: 871.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:22:29Z" - latency: 1.735924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:22:29Z" - latency: 978.314µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:21:29Z" - latency: 1.947325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:21:29Z" kind: List metadata: resourceVersion: ""