apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "31458" uid: 607e0514-504e-4668-962e-c22a6b48daae spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T16:39:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:46:56Z" - latency: 925.839µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:45:56Z" - latency: 894.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 1.364445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 888.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 813.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 991.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 1.102528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:39:56Z" - latency: 1.562269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:38:56Z" - latency: 1.119301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:37:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "29572" uid: 56361c41-b671-4ac4-91ab-57489d57c7a2 spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T16:38:56Z" message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.513285ms message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 7.361222ms message: 'load-balancer-api-external: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:44:56Z" - latency: 5.579722ms message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 8.535199ms message: 'load-balancer-api-external: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:43:56Z" - latency: 4.163522ms message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 12.225084ms message: 'load-balancer-api-external: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:42:56Z" - latency: 5.007693ms message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 6.061594ms message: 'load-balancer-api-external: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:41:56Z" - latency: 4.299369ms message: 'load-balancer-api-external: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 6.80764ms message: 'load-balancer-api-external: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "29573" uid: 33b7f8dd-2c3e-4e06-a7de-c0f4aeea846a spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T16:38:56Z" message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.516856ms message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 7.315421ms message: 'load-balancer-api-internal: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:44:56Z" - latency: 5.652694ms message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 8.595501ms message: 'load-balancer-api-internal: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:43:56Z" - latency: 4.116057ms message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 12.291846ms message: 'load-balancer-api-internal: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:42:56Z" - latency: 5.017049ms message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 6.022837ms message: 'load-balancer-api-internal: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:41:56Z" - latency: 4.259569ms message: 'load-balancer-api-internal: tcp connection to ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 6.755217ms message: 'load-balancer-api-internal: resolved host name ae5e65e5e38964d3cba4b065c8507451-0cd805d411caea37.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T16:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-129-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "31456" uid: 95f37b10-146a-409d-8cca-853e2a321de1 spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T16:39:56Z" message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.111854ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:46:56Z" - latency: 2.238611ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:45:56Z" - latency: 1.921359ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 2.195492ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 2.933739ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 1.865234ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 2.029853ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 2.12322ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:39:56Z" - latency: 2.665501ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:38:56Z" - latency: 2.086504ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:37:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-133-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "31457" uid: c77e6391-974e-4dfa-ae6a-76d540604fe6 spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T16:39:56Z" message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426678ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:46:56Z" - latency: 2.427554ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:45:56Z" - latency: 2.577079ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 2.246931ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 2.574285ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 2.600459ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 2.222193ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 2.523853ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:39:56Z" - latency: 2.780516ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:38:56Z" - latency: 2.401789ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:37:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-140-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "31455" uid: cecf6f6d-6875-4b3a-952c-d368dc8de6b8 spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T16:39:56Z" message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.007µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:46:56Z" - latency: 994.855µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:45:56Z" - latency: 894.128µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 883.804µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 930.639µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 1.23619ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 1.339826ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 949.324µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:39:56Z" - latency: 1.507356ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:38:56Z" - latency: 894.206µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:37:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T16:32:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: a494d9e1-fd4e-40e5-b3b5-c4f0fe7b4412 resourceVersion: "29569" uid: e5bcefcd-9b61-466a-8ba0-023f31237f4c spec: sourcePod: network-check-source-dbd9cf844-5g8mn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T16:38:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.202407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:44:56Z" - latency: 2.094393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T16:44:56Z" - latency: 1.364059ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:43:56Z" - latency: 1.694494ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T16:43:56Z" - latency: 4.116382ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:42:56Z" - latency: 3.704155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T16:42:56Z" - latency: 1.156727ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:41:56Z" - latency: 1.846793ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T16:41:56Z" - latency: 1.028132ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T16:40:56Z" - latency: 2.053462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T16:40:56Z" kind: List metadata: resourceVersion: ""