apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "41685" uid: 71c411f7-d802-44d0-a3b7-f170af7f1d57 spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T18:51:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 1.004598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 1.247624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 968.121µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 1.713045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:40Z" - latency: 843.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:40Z" - latency: 1.045955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:40Z" - latency: 943.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:12:40Z" - latency: 1.016386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:11:40Z" - latency: 1.194953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "42328" uid: d78e591b-420f-46fa-bdf9-a938c53af98f spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:50:40Z" message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.229564ms message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:40Z" - latency: 9.3812ms message: 'load-balancer-api-external: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:40Z" - latency: 5.460288ms message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 9.280831ms message: 'load-balancer-api-external: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:40Z" - latency: 4.689232ms message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 7.372642ms message: 'load-balancer-api-external: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:40Z" - latency: 5.061202ms message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 8.323907ms message: 'load-balancer-api-external: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:40Z" - latency: 4.672392ms message: 'load-balancer-api-external: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 8.337482ms message: 'load-balancer-api-external: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:16:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "42329" uid: 67b44ca6-e379-4526-bc88-a98b9bafa6fa spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:50:40Z" message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.154518ms message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:40Z" - latency: 9.467573ms message: 'load-balancer-api-internal: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:40Z" - latency: 5.467799ms message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 9.350603ms message: 'load-balancer-api-internal: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:40Z" - latency: 5.26315ms message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 7.418621ms message: 'load-balancer-api-internal: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:40Z" - latency: 5.072832ms message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 8.377728ms message: 'load-balancer-api-internal: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:40Z" - latency: 4.803541ms message: 'load-balancer-api-internal: tcp connection to a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 8.369813ms message: 'load-balancer-api-internal: resolved host name a4a9a72c8113642659023dfff9aff29f-20725395165c5f68.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:16:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-network-check-target-ip-10-0-132-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "41682" uid: 49e3438f-e6bd-4455-8bd3-9165b67299e7 spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:40Z" message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.409954ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 2.707879ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 2.08063ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 2.012488ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 2.669937ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:40Z" - latency: 2.362748ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:40Z" - latency: 2.226931ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:40Z" - latency: 2.711177ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:12:40Z" - latency: 2.261367ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:11:40Z" - latency: 2.240341ms message: 'network-check-target-ip-10-0-132-91: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-network-check-target-ip-10-0-135-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "41681" uid: d15d4492-a0d4-4488-ae94-a529ce62cc52 spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:40Z" message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.979µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 858.734µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 933.721µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 934.561µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 1.202184ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:40Z" - latency: 1.314942ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:40Z" - latency: 1.058527ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:40Z" - latency: 1.625667ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:12:40Z" - latency: 930.054µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:11:40Z" - latency: 833.078µs message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-network-check-target-ip-10-0-143-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "41683" uid: 75e295be-2bdd-4d0e-a661-1980d9991fde spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:40Z" message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.666998ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 2.589728ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 2.254775ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 2.433919ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 2.309038ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:40Z" - latency: 2.333126ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:40Z" - latency: 2.26861ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:40Z" - latency: 2.728965ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:12:40Z" - latency: 2.25994ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:11:40Z" - latency: 2.1782ms message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-91-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-91.ec2.internal uid: 1c4a2d96-f17d-4c6f-aa6a-7457d5dd6065 resourceVersion: "42327" uid: 7209fc08-90b3-4872-a650-5e65ef669aeb spec: sourcePod: network-check-source-869dcfcdcd-wfc8f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T18:50:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.13626ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:40Z" - latency: 1.821103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:40Z" - latency: 1.380246ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:40Z" - latency: 1.738142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:40Z" - latency: 1.136133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:40Z" - latency: 1.766753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:40Z" - latency: 1.147055ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:40Z" - latency: 1.94932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:40Z" - latency: 678.957µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:40Z" - latency: 1.894407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:16:40Z" kind: List metadata: resourceVersion: ""