apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "45163" uid: b55db398-8e61-448a-95a2-d5722fb4741d spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T15:05:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 931.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 808.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 745.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:23:29Z" - latency: 1.143045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:22:29Z" - latency: 800.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:21:29Z" - latency: 910.496µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:20:29Z" - latency: 771.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:19:29Z" - latency: 802.365µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:18:29Z" - latency: 824.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "47277" uid: 37f8c95a-d474-4e80-9c76-36b137e256c9 spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:04:29Z" message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.73975ms message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:29Z" - latency: 8.02848ms message: 'load-balancer-api-external: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:28:29Z" - latency: 3.585194ms message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:29Z" - latency: 6.833306ms message: 'load-balancer-api-external: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:27:29Z" - latency: 3.802495ms message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 6.576934ms message: 'load-balancer-api-external: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:26:29Z" - latency: 4.603035ms message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 8.361752ms message: 'load-balancer-api-external: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:25:29Z" - latency: 4.940141ms message: 'load-balancer-api-external: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 7.559057ms message: 'load-balancer-api-external: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:24:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "47278" uid: aa9a48cb-8648-47d8-bbc5-0fc874cc6dec spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:04:29Z" message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.687849ms message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:29Z" - latency: 8.002107ms message: 'load-balancer-api-internal: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:28:29Z" - latency: 4.792673ms message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:29Z" - latency: 6.894054ms message: 'load-balancer-api-internal: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:27:29Z" - latency: 4.707804ms message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 6.542389ms message: 'load-balancer-api-internal: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:26:29Z" - latency: 4.422883ms message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 8.309956ms message: 'load-balancer-api-internal: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:25:29Z" - latency: 4.955927ms message: 'load-balancer-api-internal: tcp connection to a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 7.508906ms message: 'load-balancer-api-internal: resolved host name a36944cdb86184605afe5441bd084c44-8299f482537d8776.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:24:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-network-check-target-ip-10-0-128-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "45161" uid: f13371f3-0641-40a6-a9d4-062f0b11c821 spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:05:29Z" message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.295409ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 2.173301ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 2.33402ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 2.139908ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:23:29Z" - latency: 2.137602ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:22:29Z" - latency: 2.028406ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:21:29Z" - latency: 2.153434ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:20:29Z" - latency: 2.062844ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:19:29Z" - latency: 2.214475ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:18:29Z" - latency: 2.582119ms message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-network-check-target-ip-10-0-131-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "45160" uid: aebaf5d3-5b42-484b-8c3b-87e20252b824 spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:05:29Z" message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.657µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 1.469164ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 1.207384ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 981.048µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:23:29Z" - latency: 900.966µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:22:29Z" - latency: 826.644µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:21:29Z" - latency: 873.036µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:20:29Z" - latency: 1.204283ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:19:29Z" - latency: 938.605µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:18:29Z" - latency: 754.358µs message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-network-check-target-ip-10-0-137-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "45162" uid: 761e7048-691c-47fc-8eb5-38e71536283d spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:05:29Z" message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.425749ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 2.477798ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 2.285463ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 2.373303ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:23:29Z" - latency: 2.121206ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:22:29Z" - latency: 1.99877ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:21:29Z" - latency: 2.114403ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:20:29Z" - latency: 2.301422ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:19:29Z" - latency: 2.412804ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:18:29Z" - latency: 2.475518ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T14:58:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-234.ec2.internal uid: 4efe272d-5993-4105-81b3-e4404fc08ed9 resourceVersion: "47276" uid: b84700be-36ed-4314-b49b-f155ce068203 spec: sourcePod: network-check-source-7f44b6dd87-8v9g6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T15:04:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:29Z" - latency: 2.864229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:28:29Z" - latency: 1.121972ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:29Z" - latency: 1.57985ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:27:29Z" - latency: 810.803µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:26:29Z" - latency: 1.582221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:26:29Z" - latency: 883.077µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:25:29Z" - latency: 1.664428ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:25:29Z" - latency: 830.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:24:29Z" - latency: 1.524509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:24:29Z" kind: List metadata: resourceVersion: ""