apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "44856" uid: 749dbb6e-7662-45a1-aba4-cb9807733558 spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T04:51:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 936.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 774.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 1.13955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 820.848µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:51Z" - latency: 817.777µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:51Z" - latency: 868.004µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:51Z" - latency: 1.205961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:06:51Z" - latency: 863.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:05:51Z" - latency: 970.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:04:51Z" - latency: 757.149µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "47286" uid: 41cd3d52-00f4-449f-9e9d-a2e9c7e9a1d1 spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T04:50:51Z" message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.309798ms message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:51Z" - latency: 8.397219ms message: 'load-balancer-api-external: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:51Z" - latency: 4.510478ms message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:51Z" - latency: 10.630469ms message: 'load-balancer-api-external: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:13:51Z" - latency: 4.479714ms message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 8.585721ms message: 'load-balancer-api-external: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:12:51Z" - latency: 3.851892ms message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 8.635ms message: 'load-balancer-api-external: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:11:51Z" - latency: 4.162822ms message: 'load-balancer-api-external: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 8.629228ms message: 'load-balancer-api-external: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:10:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "47285" uid: dd6d3aef-4984-41a1-af4e-71bf9e00221d spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T04:50:51Z" message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.328709ms message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:51Z" - latency: 8.458654ms message: 'load-balancer-api-internal: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:51Z" - latency: 6.00329ms message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:51Z" - latency: 10.706548ms message: 'load-balancer-api-internal: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:13:51Z" - latency: 3.415294ms message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 8.680849ms message: 'load-balancer-api-internal: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:12:51Z" - latency: 4.607341ms message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 8.708925ms message: 'load-balancer-api-internal: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:11:51Z" - latency: 3.847282ms message: 'load-balancer-api-internal: tcp connection to ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 8.677765ms message: 'load-balancer-api-internal: resolved host name ad86a03da5b4c4b52a31b3667eb62140-0a9673a961fc5c4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:10:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-135-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "44854" uid: 4daf7167-7c58-4816-9854-0d5dbb2f75ea spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:51:51Z" message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039408ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 2.080272ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 2.258553ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 1.983955ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:51Z" - latency: 2.314605ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:51Z" - latency: 2.132843ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:51Z" - latency: 2.205308ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:06:51Z" - latency: 2.485675ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:05:51Z" - latency: 2.259656ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:04:51Z" - latency: 2.139087ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-137-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "44855" uid: 82963f0a-6452-4ee6-946d-0354bf1b1754 spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:51:51Z" message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.85662ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 1.812853ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 1.62871ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 1.35018ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:51Z" - latency: 1.814858ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:51Z" - latency: 1.545401ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:51Z" - latency: 1.860482ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:06:51Z" - latency: 1.992008ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:05:51Z" - latency: 1.728783ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:04:51Z" - latency: 1.68287ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-139-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "44853" uid: eba8de81-4cfd-421b-98e0-be68446b2adb spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:51:51Z" message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.331µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 938.095µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 901.43µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 795.297µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:51Z" - latency: 838.602µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:51Z" - latency: 786.435µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:51Z" - latency: 795.664µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:06:51Z" - latency: 1.217772ms message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:05:51Z" - latency: 1.328548ms message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:04:51Z" - latency: 1.110985ms message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 931e34b3-f13e-494a-ad05-c5fbeba5aaeb resourceVersion: "47284" uid: 0aa2a551-e0c5-48c6-9a31-3b2b9c4b8c2c spec: sourcePod: network-check-source-56d84b9f44-wxlcm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T04:50:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.376051ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:51Z" - latency: 1.702045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:51Z" - latency: 1.519875ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:51Z" - latency: 2.863291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:13:51Z" - latency: 1.024168ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:51Z" - latency: 2.140887ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:12:51Z" - latency: 802.338µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:51Z" - latency: 1.745429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:11:51Z" - latency: 964.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:51Z" - latency: 2.325627ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:10:51Z" kind: List metadata: resourceVersion: ""