apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "51158" uid: 1ede37f0-26f3-46fa-b5c8-1b096494717c spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T21:09:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.080175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 1.09406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 1.046883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 825.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 859.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:21Z" - latency: 868.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:21Z" - latency: 1.060748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:21Z" - latency: 1.15508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:30:21Z" - latency: 1.143507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:29:21Z" - latency: 1.0236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "52038" uid: 3f54e7fb-5cac-462b-95a5-e40b42e9eb95 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T21:08:21Z" message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.815209ms message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:21Z" - latency: 7.847098ms message: 'load-balancer-api-external: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:38:21Z" - latency: 4.515231ms message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 9.01471ms message: 'load-balancer-api-external: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:21Z" - latency: 5.679248ms message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 9.158325ms message: 'load-balancer-api-external: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:21Z" - latency: 4.338628ms message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 8.809756ms message: 'load-balancer-api-external: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:21Z" - latency: 5.048981ms message: 'load-balancer-api-external: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 7.497681ms message: 'load-balancer-api-external: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "52037" uid: 4387a7b6-1c6b-466c-9a3c-9073ee7c0f49 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T21:08:21Z" message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.239318ms message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:21Z" - latency: 7.810713ms message: 'load-balancer-api-internal: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:38:21Z" - latency: 5.505707ms message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 9.199387ms message: 'load-balancer-api-internal: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:21Z" - latency: 5.681549ms message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 9.102019ms message: 'load-balancer-api-internal: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:21Z" - latency: 6.111143ms message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 8.868976ms message: 'load-balancer-api-internal: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:21Z" - latency: 5.472209ms message: 'load-balancer-api-internal: tcp connection to a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 7.549401ms message: 'load-balancer-api-internal: resolved host name a4a4bc3320459496887145aa07756a11-cfa2d891997baa6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-131-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "51154" uid: 14c00150-72ae-48c6-b7f4-1250b059c937 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:09:21Z" message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.377µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 1.03969ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 1.341836ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 959.493µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 897.049µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:21Z" - latency: 866.46µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:21Z" - latency: 1.447608ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:21Z" - latency: 1.381026ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:30:21Z" - latency: 943.799µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:29:21Z" - latency: 948.219µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-136-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "51156" uid: f9f304ae-ebc5-473f-88ef-1adab0bcee32 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:09:21Z" message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222675ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 2.774242ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 2.327614ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 2.443228ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 2.554596ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:21Z" - latency: 2.208764ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:21Z" - latency: 2.577205ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:21Z" - latency: 2.480122ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:30:21Z" - latency: 2.620468ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:29:21Z" - latency: 2.455001ms message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-136-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "51155" uid: 93bca209-1573-4c7d-aa07-1e56b1a0fa00 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:09:21Z" message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.493905ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 2.714439ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 2.49275ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 2.842139ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 2.221178ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:21Z" - latency: 2.189534ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:21Z" - latency: 2.650116ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:21Z" - latency: 2.464612ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:30:21Z" - latency: 2.673986ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:29:21Z" - latency: 2.73677ms message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:02:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: df6fe118-ad4e-4ee8-8761-97b86f7eb3d1 resourceVersion: "52036" uid: a69d2436-0445-49ff-8c30-f020e9339c10 spec: sourcePod: network-check-source-989f8b8dc-jw6qp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T21:08:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:21Z" - latency: 1.622159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:38:21Z" - latency: 1.257423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:21Z" - latency: 2.042924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:21Z" - latency: 868.757µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:21Z" - latency: 1.869368ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:21Z" - latency: 950.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:21Z" - latency: 1.784342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:21Z" - latency: 1.044793ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:21Z" - latency: 1.71449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:21Z" kind: List metadata: resourceVersion: ""