apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "40312" uid: b8949901-b729-47e7-a2a5-c10fea737e5c spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-25T00:06:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:55:44Z" - latency: 861.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:54:44Z" - latency: 872.045µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 909.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 840.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 1.351547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 862.5µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 865.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:48:44Z" - latency: 848.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:47:44Z" - latency: 944.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:46:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "39368" uid: 2d6e09b0-bb9a-4d2e-99a6-cb5fd03d74fc spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-25T00:05:44Z" message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.86318ms message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 7.059349ms message: 'load-balancer-api-external: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:53:44Z" - latency: 4.759899ms message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 6.366708ms message: 'load-balancer-api-external: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:52:44Z" - latency: 4.920391ms message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 6.49302ms message: 'load-balancer-api-external: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:51:44Z" - latency: 5.101793ms message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 6.315115ms message: 'load-balancer-api-external: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:50:44Z" - latency: 4.216971ms message: 'load-balancer-api-external: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 6.447505ms message: 'load-balancer-api-external: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:49:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "39369" uid: 35143395-7ea0-4b62-ba6f-7aeb1757e721 spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-25T00:05:44Z" message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.039184ms message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 7.116074ms message: 'load-balancer-api-internal: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:53:44Z" - latency: 4.740597ms message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 6.36152ms message: 'load-balancer-api-internal: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:52:44Z" - latency: 4.53886ms message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 6.529858ms message: 'load-balancer-api-internal: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:51:44Z" - latency: 5.025279ms message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 6.280028ms message: 'load-balancer-api-internal: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:50:44Z" - latency: 4.247787ms message: 'load-balancer-api-internal: tcp connection to a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 6.42062ms message: 'load-balancer-api-internal: resolved host name a1fdc972c633349e2a8c6d272b6b4bc3-6f62bd65bdfff2d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-25T00:49:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-128-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "40309" uid: f533bcdc-b780-4d5e-959e-29efa3dd5213 spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-25T00:06:44Z" message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 798.37µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:55:44Z" - latency: 911.238µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:54:44Z" - latency: 759.977µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 838.646µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 793.289µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 979.06µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 1.020379ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 1.015274ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:48:44Z" - latency: 820.967µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:47:44Z" - latency: 887.296µs message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:46:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-129-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "40311" uid: de2eb6fa-eef4-468a-9717-39871d36c800 spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-25T00:06:44Z" message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.151887ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:55:44Z" - latency: 2.176405ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:54:44Z" - latency: 2.094184ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 2.0658ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 2.109226ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 2.105088ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 1.941666ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 1.930125ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:48:44Z" - latency: 2.160078ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:47:44Z" - latency: 2.167491ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:46:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-140-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "40310" uid: ef17ceed-1bd0-4066-841e-5a827fced444 spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-25T00:06:44Z" message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.824338ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:55:44Z" - latency: 2.194323ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:54:44Z" - latency: 2.135916ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 2.43088ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 2.236451ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 2.218296ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 2.116935ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 2.205486ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:48:44Z" - latency: 2.17464ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:47:44Z" - latency: 2.207266ms message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:46:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T23:59:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-234.ec2.internal uid: e0053b9f-078c-4ffa-9960-2ab09d665fc9 resourceVersion: "39367" uid: eec817ee-caeb-450d-b0ba-e40a4b3d9f5a spec: sourcePod: network-check-source-8894fc9bd-v4tzb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-25T00:05:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.295µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:53:44Z" - latency: 1.700841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-25T00:53:44Z" - latency: 1.022193ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:52:44Z" - latency: 1.761431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-25T00:52:44Z" - latency: 889.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:51:44Z" - latency: 1.584431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-25T00:51:44Z" - latency: 941.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:50:44Z" - latency: 1.614297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-25T00:50:44Z" - latency: 837.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-25T00:49:44Z" - latency: 1.613033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-25T00:49:44Z" kind: List metadata: resourceVersion: ""