apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "20581" uid: b4f122e1-625b-4411-8ce2-e951ce16d2fe spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T12:03:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.335µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 1.077208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 1.089884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:15:09Z" - latency: 976.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:14:09Z" - latency: 1.130423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:13:09Z" - latency: 1.118837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:12:09Z" - latency: 981.28µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:11:09Z" - latency: 1.493337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:09Z" - latency: 1.198486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:09Z" - latency: 1.08586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "22194" uid: 1331491f-2eb9-4bfb-9513-647e5d793525 spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:02:09Z" message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.830482ms message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:20:09Z" - latency: 9.025646ms message: 'load-balancer-api-external: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:20:09Z" - latency: 4.594992ms message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:19:09Z" - latency: 9.097748ms message: 'load-balancer-api-external: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:19:09Z" - latency: 4.681932ms message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:18:09Z" - latency: 8.979774ms message: 'load-balancer-api-external: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:18:09Z" - latency: 4.892797ms message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 9.550848ms message: 'load-balancer-api-external: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:17:09Z" - latency: 5.278528ms message: 'load-balancer-api-external: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 14.21255ms message: 'load-balancer-api-external: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "22193" uid: cd6133ce-a410-45c7-875a-4938c7c2bce9 spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:02:09Z" message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.759187ms message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:20:09Z" - latency: 9.053174ms message: 'load-balancer-api-internal: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:20:09Z" - latency: 4.757744ms message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:19:09Z" - latency: 9.181466ms message: 'load-balancer-api-internal: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:19:09Z" - latency: 4.490481ms message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:18:09Z" - latency: 8.935932ms message: 'load-balancer-api-internal: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:18:09Z" - latency: 4.904446ms message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 9.535334ms message: 'load-balancer-api-internal: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:17:09Z" - latency: 5.261187ms message: 'load-balancer-api-internal: tcp connection to a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 14.166614ms message: 'load-balancer-api-internal: resolved host name a811eb45468f24a4f93ff8de78b7531b-058e737beaadb9ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-network-check-target-ip-10-0-129-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "20580" uid: e7e84af1-beb1-4119-8f53-407643acd96f spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:03:09Z" message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.029851ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 1.971926ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 2.17503ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:15:09Z" - latency: 2.161061ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:14:09Z" - latency: 2.172495ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:13:09Z" - latency: 2.209475ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:12:09Z" - latency: 2.25212ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:11:09Z" - latency: 2.494461ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:09Z" - latency: 2.123412ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:09Z" - latency: 2.255806ms message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-network-check-target-ip-10-0-134-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "20579" uid: eca26e09-d57a-44ef-be55-8fe8b08f23a1 spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:03:09Z" message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.331819ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 1.967725ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 2.315942ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:15:09Z" - latency: 2.591083ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:14:09Z" - latency: 2.238306ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:13:09Z" - latency: 2.164706ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:12:09Z" - latency: 2.348178ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:11:09Z" - latency: 2.257266ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:09Z" - latency: 2.364768ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:09Z" - latency: 2.219408ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-network-check-target-ip-10-0-136-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "20578" uid: 600e265f-0c86-4a54-b2c2-71467a33d0c1 spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:03:09Z" message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 728.523µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 804.488µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 873.11µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:15:09Z" - latency: 1.548278ms message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:14:09Z" - latency: 891.795µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:13:09Z" - latency: 796.811µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:12:09Z" - latency: 998.497µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:11:09Z" - latency: 993.125µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:09Z" - latency: 997.167µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:09Z" - latency: 930.548µs message: 'network-check-target-ip-10-0-136-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:56:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-189.ec2.internal uid: a5ca758c-c0b2-4b04-a3cc-47cb367c24c6 resourceVersion: "22192" uid: c6cdf895-a723-4c4d-afd1-4ebb61821a34 spec: sourcePod: network-check-source-dbd9cf844-wrn8q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T12:02:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.479µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:20:09Z" - latency: 1.664013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:20:09Z" - latency: 815.211µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:19:09Z" - latency: 1.790868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:19:09Z" - latency: 895.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:18:09Z" - latency: 1.873633ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:18:09Z" - latency: 722.966µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:17:09Z" - latency: 2.703192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:17:09Z" - latency: 956.464µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:16:09Z" - latency: 1.748446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:16:09Z" kind: List metadata: resourceVersion: ""