apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156336" uid: 78e7e0a2-8313-4f8d-90ce-bb1ac7289889 spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:14:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 1.001823ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 1.360411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 835.055µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 1.109334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:08Z" - latency: 1.352407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:08Z" - latency: 22.314513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:08Z" - latency: 1.036296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:08Z" - latency: 1.337749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:08Z" - latency: 1.491905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156913" uid: 6456741d-663f-4ab5-9f26-d1f1eb28f995 spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:13:08Z" message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.3721ms message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:08Z" - latency: 6.900007ms message: 'load-balancer-api-external: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:25:08Z" - latency: 16.637655ms message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 7.506528ms message: 'load-balancer-api-external: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:24:08Z" - latency: 15.932994ms message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 7.437953ms message: 'load-balancer-api-external: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:23:08Z" - latency: 17.895027ms message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 8.282484ms message: 'load-balancer-api-external: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:22:08Z" - latency: 16.119382ms message: 'load-balancer-api-external: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 6.818383ms message: 'load-balancer-api-external: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:21:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156914" uid: 3d9fe593-35ff-46f8-aa41-a4f0671b83fb spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:13:08Z" message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.395487ms message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:08Z" - latency: 6.958808ms message: 'load-balancer-api-internal: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:25:08Z" - latency: 16.723198ms message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 7.564343ms message: 'load-balancer-api-internal: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:24:08Z" - latency: 15.94624ms message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 7.393843ms message: 'load-balancer-api-internal: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:23:08Z" - latency: 18.764967ms message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 8.338751ms message: 'load-balancer-api-internal: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:22:08Z" - latency: 17.112399ms message: 'load-balancer-api-internal: tcp connection to a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 6.772037ms message: 'load-balancer-api-internal: resolved host name a484145a9e3ca4e29b2f4db5a47bc15e-0d1ad5d6b3e7032c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:21:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-network-check-target-ip-10-0-130-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156335" uid: 31ae2131-3939-4265-b382-05d57d9f8213 spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:14:08Z" message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287888ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 2.410244ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 2.626548ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 2.359687ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 2.638006ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:08Z" - latency: 2.288867ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:08Z" - latency: 12.109154ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:08Z" - latency: 2.585013ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:08Z" - latency: 2.512383ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:08Z" - latency: 2.723937ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-network-check-target-ip-10-0-135-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156334" uid: 48d3f593-15f5-4b72-9ddf-98b042a33ad5 spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:14:08Z" message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.195995ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 2.30943ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 2.392272ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 2.123578ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 2.520287ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:08Z" - latency: 2.474175ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:08Z" - latency: 11.887891ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:08Z" - latency: 2.623064ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:08Z" - latency: 2.292546ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:08Z" - latency: 2.58104ms message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-network-check-target-ip-10-0-140-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156333" uid: 09123f1d-b359-4ad1-b508-d92b5b30593f spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:14:08Z" message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.578µs message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 1.138577ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 1.653781ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 1.003278ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 1.352255ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:08Z" - latency: 1.220512ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:08Z" - latency: 22.532862ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:08Z" - latency: 1.566ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:08Z" - latency: 940.933µs message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:08Z" - latency: 1.236048ms message: 'network-check-target-ip-10-0-140-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:07:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-235-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-235.ec2.internal uid: bb6ce2fb-cceb-4a43-be23-2d11c6740861 resourceVersion: "156911" uid: bcfa78b8-ae3d-4508-b79b-86e0bff963fc spec: sourcePod: network-check-source-6f78d59f99-cfdmh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:13:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.430407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:08Z" - latency: 1.791155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:25:08Z" - latency: 835.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:24:08Z" - latency: 2.521572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:24:08Z" - latency: 1.019412ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:23:08Z" - latency: 1.97381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:23:08Z" - latency: 1.074457ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:22:08Z" - latency: 1.89916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:22:08Z" - latency: 956.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:08Z" - latency: 1.759859ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:21:08Z" kind: List metadata: resourceVersion: ""