apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "44217" uid: a47f8dea-b47e-4c17-9fbf-63bff917ca67 spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T17:15:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.662µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 1.079161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 787.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 1.358582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:33:56Z" - latency: 850.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:32:56Z" - latency: 742.119µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:31:56Z" - latency: 1.232272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:30:56Z" - latency: 1.549556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:29:56Z" - latency: 874.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:28:56Z" - latency: 1.097951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "46474" uid: ca82012b-ffae-4ddb-8d75-087bb0b8d764 spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T17:14:56Z" message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.558157ms message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:38:56Z" - latency: 8.386453ms message: 'load-balancer-api-external: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:38:56Z" - latency: 4.017163ms message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:37:56Z" - latency: 7.661794ms message: 'load-balancer-api-external: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:37:56Z" - latency: 4.679795ms message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 7.702209ms message: 'load-balancer-api-external: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:36:56Z" - latency: 6.760064ms message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 7.643978ms message: 'load-balancer-api-external: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:35:56Z" - latency: 4.102899ms message: 'load-balancer-api-external: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 8.1333ms message: 'load-balancer-api-external: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:34:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "46475" uid: 1a308c9b-9c3e-47f9-a9f8-9616f81e06fb spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T17:14:56Z" message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.787797ms message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:38:56Z" - latency: 8.311285ms message: 'load-balancer-api-internal: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:38:56Z" - latency: 4.012059ms message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:37:56Z" - latency: 7.798279ms message: 'load-balancer-api-internal: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:37:56Z" - latency: 3.637331ms message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 7.523713ms message: 'load-balancer-api-internal: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:36:56Z" - latency: 6.19896ms message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 7.5961ms message: 'load-balancer-api-internal: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:35:56Z" - latency: 4.085485ms message: 'load-balancer-api-internal: tcp connection to a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 8.210441ms message: 'load-balancer-api-internal: resolved host name a22e6d64c219b4de19d26fb19f23d841-e2a24555a602c220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T17:34:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-network-check-target-ip-10-0-128-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "44214" uid: 309dd178-edd6-429f-a757-4522a60a3d50 spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:15:56Z" message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.121992ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 2.09138ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 2.202752ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 2.385561ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:33:56Z" - latency: 2.396853ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:32:56Z" - latency: 2.100851ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:31:56Z" - latency: 2.193532ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:30:56Z" - latency: 2.176672ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:29:56Z" - latency: 2.372433ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:28:56Z" - latency: 2.548913ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-network-check-target-ip-10-0-134-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "44216" uid: cd69dc7c-323d-4652-98e5-f927213fae39 spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:15:56Z" message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.576µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 841.111µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 849.339µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 825.734µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:33:56Z" - latency: 890.64µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:32:56Z" - latency: 653.09µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:31:56Z" - latency: 726.244µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:30:56Z" - latency: 787.159µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:29:56Z" - latency: 746.445µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:28:56Z" - latency: 802.81µs message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-network-check-target-ip-10-0-136-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "44215" uid: 8642b6ff-6b5a-4748-8bcc-a99432109c0a spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:15:56Z" message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911613ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 2.029471ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 2.686711ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 2.227722ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:33:56Z" - latency: 2.241859ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:32:56Z" - latency: 2.046062ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:31:56Z" - latency: 2.253245ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:30:56Z" - latency: 2.775517ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:29:56Z" - latency: 2.231553ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:28:56Z" - latency: 2.695066ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:08:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-95.ec2.internal uid: 89aca98a-61ac-4234-9edd-15941bacd281 resourceVersion: "46473" uid: e6a0cc25-2e50-4c74-ab58-63cf4117034d spec: sourcePod: network-check-source-7f44b6dd87-pgxqf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T17:14:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.801µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:38:56Z" - latency: 2.197784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T17:38:56Z" - latency: 1.088582ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:37:56Z" - latency: 1.75249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T17:37:56Z" - latency: 833.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:36:56Z" - latency: 1.755078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T17:36:56Z" - latency: 832.739µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:35:56Z" - latency: 1.839664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T17:35:56Z" - latency: 1.12784ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T17:34:56Z" - latency: 1.600801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T17:34:56Z" kind: List metadata: resourceVersion: ""