apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "46392" uid: e866e7fd-6dd0-4bdb-a4d6-50545cb0701f spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T16:04:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.734µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 1.393914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 1.47055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 1.290591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:22:15Z" - latency: 832.332µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:21:15Z" - latency: 962.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:20:15Z" - latency: 1.038768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:19:15Z" - latency: 1.019325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:18:15Z" - latency: 902.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:17:15Z" - latency: 1.485533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:16:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "48591" uid: ea63639f-18a7-4e97-a611-462a146ec9e7 spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T16:03:15Z" message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.002783ms message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:27:15Z" - latency: 7.461146ms message: 'load-balancer-api-external: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:27:15Z" - latency: 6.010036ms message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:26:15Z" - latency: 7.192197ms message: 'load-balancer-api-external: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:26:15Z" - latency: 5.538484ms message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 7.477813ms message: 'load-balancer-api-external: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:25:15Z" - latency: 5.955449ms message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 9.092582ms message: 'load-balancer-api-external: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:24:15Z" - latency: 5.219612ms message: 'load-balancer-api-external: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 6.91746ms message: 'load-balancer-api-external: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:23:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "48592" uid: c4f3f530-02c6-488d-ae2e-67f561b32850 spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T16:03:15Z" message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.442894ms message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:27:15Z" - latency: 7.578792ms message: 'load-balancer-api-internal: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:27:15Z" - latency: 6.291169ms message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:26:15Z" - latency: 7.255411ms message: 'load-balancer-api-internal: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:26:15Z" - latency: 5.484901ms message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 7.552747ms message: 'load-balancer-api-internal: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:25:15Z" - latency: 5.982806ms message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 9.193767ms message: 'load-balancer-api-internal: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:24:15Z" - latency: 5.407428ms message: 'load-balancer-api-internal: tcp connection to a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 6.952805ms message: 'load-balancer-api-internal: resolved host name a6dc9231110b64741b4dbbcc771bdd01-02ad1774dcca40c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:23:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-136-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "46389" uid: 78bb04eb-a114-4350-a184-e37cfae32262 spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:04:15Z" message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.03107ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 832.629µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 2.048975ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 1.10819ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:22:15Z" - latency: 864.393µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:21:15Z" - latency: 1.195025ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:20:15Z" - latency: 1.615607ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:19:15Z" - latency: 1.316192ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:18:15Z" - latency: 1.04093ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:17:15Z" - latency: 1.339264ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:16:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-138-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "46390" uid: 19c835f0-0515-4a11-9841-ae2cc3db0d53 spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:04:15Z" message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.051663ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 1.974691ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 2.919473ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 2.32709ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:22:15Z" - latency: 1.992467ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:21:15Z" - latency: 2.167842ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:20:15Z" - latency: 2.204988ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:19:15Z" - latency: 2.356311ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:18:15Z" - latency: 2.28681ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:17:15Z" - latency: 2.499548ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:16:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-140-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "46391" uid: d665c0e2-3661-4ac9-ac12-7f492e62b640 spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:04:15Z" message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.399884ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 2.105193ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 2.67845ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 2.213365ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:22:15Z" - latency: 2.073001ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:21:15Z" - latency: 2.27565ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:20:15Z" - latency: 2.12669ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:19:15Z" - latency: 2.363451ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:18:15Z" - latency: 2.175834ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:17:15Z" - latency: 2.177957ms message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:16:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: 7b3bd76d-d146-4307-ad25-ef47de2276f2 resourceVersion: "48589" uid: edf37306-482a-4317-90a7-11731e718b7b spec: sourcePod: network-check-source-dbd9cf844-gvrln targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T16:03:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:27:15Z" - latency: 2.216079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:27:15Z" - latency: 890.849µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:26:15Z" - latency: 1.823769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:26:15Z" - latency: 908.408µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:25:15Z" - latency: 2.085967ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:25:15Z" - latency: 1.426663ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:24:15Z" - latency: 1.731296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:24:15Z" - latency: 996.044µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:23:15Z" - latency: 2.123199ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:23:15Z" kind: List metadata: resourceVersion: ""