apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "39176" uid: 91e7cbdf-6cb3-4c9c-92a4-eac3891823f7 spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T14:03:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.310874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 1.173387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 1.101367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 801.102µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:21:22Z" - latency: 1.376182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:20:22Z" - latency: 1.099386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:19:22Z" - latency: 1.242142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:18:22Z" - latency: 1.014069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:17:22Z" - latency: 1.142122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:16:22Z" - latency: 1.157936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "40650" uid: a8bd5283-e768-424a-8e4c-56be446db6b8 spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:02:22Z" message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.824012ms message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:26:22Z" - latency: 8.434773ms message: 'load-balancer-api-external: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:26:22Z" - latency: 5.457364ms message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:25:22Z" - latency: 9.268738ms message: 'load-balancer-api-external: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:25:22Z" - latency: 3.900434ms message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 8.612538ms message: 'load-balancer-api-external: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:24:22Z" - latency: 4.973143ms message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 8.772185ms message: 'load-balancer-api-external: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:23:22Z" - latency: 6.907088ms message: 'load-balancer-api-external: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 8.16684ms message: 'load-balancer-api-external: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "40649" uid: a5d8c8c9-ec91-4828-bede-70e08ce33797 spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:02:22Z" message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.881977ms message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:26:22Z" - latency: 8.465494ms message: 'load-balancer-api-internal: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:26:22Z" - latency: 5.65527ms message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:25:22Z" - latency: 9.30072ms message: 'load-balancer-api-internal: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:25:22Z" - latency: 3.928094ms message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 8.579982ms message: 'load-balancer-api-internal: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:24:22Z" - latency: 4.967935ms message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 8.609391ms message: 'load-balancer-api-internal: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:23:22Z" - latency: 5.671374ms message: 'load-balancer-api-internal: tcp connection to a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 8.136505ms message: 'load-balancer-api-internal: resolved host name a018c87b6a35d41f581ac820e9c70490-371574b2b8aa433d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-129-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "39175" uid: e6bfb1fc-c40c-471e-a0a9-350b47ae25de spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:03:22Z" message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.215355ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 2.250321ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 2.388623ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 2.109192ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:21:22Z" - latency: 2.020809ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:20:22Z" - latency: 2.373079ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:19:22Z" - latency: 2.253694ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:18:22Z" - latency: 2.34255ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:17:22Z" - latency: 2.24656ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:16:22Z" - latency: 2.336601ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-140-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "39174" uid: 336d44f9-676a-49a2-a57d-1f5d7561a76b spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:03:22Z" message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.120904ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 1.763367ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 1.812866ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 1.65787ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:21:22Z" - latency: 1.650174ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:20:22Z" - latency: 1.920177ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:19:22Z" - latency: 1.717496ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:18:22Z" - latency: 1.7937ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:17:22Z" - latency: 1.714503ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:16:22Z" - latency: 1.772613ms message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-network-check-target-ip-10-0-141-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "39173" uid: 1bbf65ee-7979-47e9-b4b3-cd2940f0aa31 spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:03:22Z" message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245537ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 884.376µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 1.043291ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 773.709µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:21:22Z" - latency: 848.761µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:20:22Z" - latency: 987.203µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:19:22Z" - latency: 967.484µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:18:22Z" - latency: 866.008µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:17:22Z" - latency: 1.264105ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:16:22Z" - latency: 829.846µs message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:56:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-251.ec2.internal uid: 921b82d0-d031-481a-b2fe-035252635ee3 resourceVersion: "40647" uid: 978e3054-5e57-4f42-b04e-e7d337536e0c spec: sourcePod: network-check-source-7f44b6dd87-h5p4t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T14:02:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 927.553µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:26:22Z" - latency: 1.724938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:26:22Z" - latency: 966.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:25:22Z" - latency: 1.719359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:25:22Z" - latency: 1.020068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:24:22Z" - latency: 2.189516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:24:22Z" - latency: 876.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:23:22Z" - latency: 1.847577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:23:22Z" - latency: 891.342µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:22:22Z" - latency: 1.831952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:22:22Z" kind: List metadata: resourceVersion: ""