apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "39883" uid: 3e4964f5-96ce-4cf5-a6aa-3b10e2124ac5 spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T12:25:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.160199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 734.792µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:13:52Z" - latency: 987.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:12:52Z" - latency: 1.105972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:11:52Z" - latency: 1.22018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:10:52Z" - latency: 939.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:09:52Z" - latency: 1.307835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:08:52Z" - latency: 1.340215ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:07:52Z" - latency: 912.067µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:06:52Z" - latency: 1.386671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:05:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "41958" uid: f4871414-6b9f-44a9-a5cb-4ad736fbb173 spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T12:24:52Z" message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.076109ms message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:18:52Z" - latency: 6.480335ms message: 'load-balancer-api-external: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:18:52Z" - latency: 5.194198ms message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:17:52Z" - latency: 5.99718ms message: 'load-balancer-api-external: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:17:52Z" - latency: 5.442962ms message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:16:52Z" - latency: 6.603183ms message: 'load-balancer-api-external: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:16:52Z" - latency: 5.621526ms message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:15:52Z" - latency: 6.359721ms message: 'load-balancer-api-external: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:15:52Z" - latency: 4.829243ms message: 'load-balancer-api-external: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 8.26384ms message: 'load-balancer-api-external: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:14:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "41957" uid: 94d4628e-5a4c-45c5-9e0c-aad4de0117bb spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T12:24:52Z" message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.98269ms message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:18:52Z" - latency: 6.511574ms message: 'load-balancer-api-internal: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:18:52Z" - latency: 6.472286ms message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:17:52Z" - latency: 5.931491ms message: 'load-balancer-api-internal: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:17:52Z" - latency: 4.924304ms message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:16:52Z" - latency: 6.630166ms message: 'load-balancer-api-internal: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:16:52Z" - latency: 5.587876ms message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:15:52Z" - latency: 6.406386ms message: 'load-balancer-api-internal: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:15:52Z" - latency: 4.850907ms message: 'load-balancer-api-internal: tcp connection to a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 8.317453ms message: 'load-balancer-api-internal: resolved host name a61faeadf567d4caca4c8abd58746ce7-d703e1bb5ed104cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:14:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-network-check-target-ip-10-0-132-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "39880" uid: d73ebb12-98da-4b34-9212-c96ae89598aa spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:25:52Z" message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.823225ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 1.75616ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:13:52Z" - latency: 1.752705ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:12:52Z" - latency: 1.927531ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:11:52Z" - latency: 1.880387ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:10:52Z" - latency: 1.75674ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:09:52Z" - latency: 2.291754ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:08:52Z" - latency: 1.926102ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:07:52Z" - latency: 1.655213ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:06:52Z" - latency: 2.109287ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:05:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-network-check-target-ip-10-0-134-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "39881" uid: 07d695f2-5014-426e-ba20-617dc7f1750a spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:25:52Z" message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.383285ms message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 698.482µs message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:13:52Z" - latency: 828.699µs message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:12:52Z" - latency: 852.108µs message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:11:52Z" - latency: 785.959µs message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:10:52Z" - latency: 1.088567ms message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:09:52Z" - latency: 1.524334ms message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:08:52Z" - latency: 1.517915ms message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:07:52Z" - latency: 1.007242ms message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:06:52Z" - latency: 816.132µs message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:05:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-network-check-target-ip-10-0-141-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "39882" uid: 06cbbea7-52b9-4f25-b2ca-9fc39913a6e2 spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:25:52Z" message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.025494ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 2.129223ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:13:52Z" - latency: 2.136678ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:12:52Z" - latency: 2.133645ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:11:52Z" - latency: 1.942875ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:10:52Z" - latency: 2.140455ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:09:52Z" - latency: 2.413314ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:08:52Z" - latency: 1.951583ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:07:52Z" - latency: 2.019712ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:06:52Z" - latency: 2.156691ms message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:05:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:18:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-255-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-255.ec2.internal uid: 7fb921b6-d24b-46ad-9ae5-036463e71c77 resourceVersion: "41956" uid: 0d183c13-02fc-45cf-b5b0-6f83ce2016fd spec: sourcePod: network-check-source-7f44b6dd87-t97h9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T12:24:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.416µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:18:52Z" - latency: 1.703816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:18:52Z" - latency: 838.267µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:17:52Z" - latency: 1.620802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:17:52Z" - latency: 909.029µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:16:52Z" - latency: 1.7309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:16:52Z" - latency: 1.026073ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:15:52Z" - latency: 1.750643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:15:52Z" - latency: 755.761µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:14:52Z" - latency: 1.683556ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:14:52Z" kind: List metadata: resourceVersion: ""