apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32606" uid: fb404969-db5c-4364-b52e-e1b95ec66460 spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T16:44:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 727.355µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 1.003554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 730.1µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 880.938µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 894.381µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 886.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:14:10Z" - latency: 871.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:13:10Z" - latency: 775.662µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:12:10Z" - latency: 861.241µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:11:10Z" - latency: 1.014839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:10:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32608" uid: 2423f379-b211-4157-8464-75e5d2f5ce68 spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:43:10Z" message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.137113ms message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 8.299965ms message: 'load-balancer-api-external: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:19:10Z" - latency: 5.209765ms message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 8.935963ms message: 'load-balancer-api-external: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:18:10Z" - latency: 5.689647ms message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 7.279269ms message: 'load-balancer-api-external: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:17:10Z" - latency: 5.260265ms message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 10.916624ms message: 'load-balancer-api-external: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:16:10Z" - latency: 5.079751ms message: 'load-balancer-api-external: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 8.56891ms message: 'load-balancer-api-external: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:15:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32607" uid: 1fa08015-a23d-4f16-8439-9845e9c5b416 spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:43:10Z" message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.246815ms message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 8.204549ms message: 'load-balancer-api-internal: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:19:10Z" - latency: 5.58065ms message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 8.954044ms message: 'load-balancer-api-internal: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:18:10Z" - latency: 5.733297ms message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 7.161661ms message: 'load-balancer-api-internal: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:17:10Z" - latency: 4.452594ms message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 10.850839ms message: 'load-balancer-api-internal: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:16:10Z" - latency: 5.125433ms message: 'load-balancer-api-internal: tcp connection to ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 8.49246ms message: 'load-balancer-api-internal: resolved host name ac1057841090540489b37d5f49013be2-9258a56c15620f27.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:15:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-129-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32605" uid: 3496d400-ca8f-45dd-8d9a-3df19348e9df spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:44:10Z" message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.126009ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 2.068389ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 1.590984ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 2.058179ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 2.798884ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 1.925879ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:14:10Z" - latency: 2.092515ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:13:10Z" - latency: 1.677756ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:12:10Z" - latency: 1.965217ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:11:10Z" - latency: 2.430153ms message: 'network-check-target-ip-10-0-129-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:10:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-138-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32604" uid: 3d2da4e6-f10b-4fb3-b7ab-93b4b7584efb spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:44:10Z" message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.115301ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 1.971194ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 1.983359ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 1.893804ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 2.040832ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 2.149436ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:14:10Z" - latency: 2.031756ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:13:10Z" - latency: 1.998149ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:12:10Z" - latency: 2.325902ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:11:10Z" - latency: 2.311542ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:10:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-138-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32602" uid: 766e8494-7213-4db9-925f-248cd3d886ea spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:44:10Z" message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.036µs message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 1.133408ms message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 1.23447ms message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 1.197375ms message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 1.125908ms message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 895.375µs message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:14:10Z" - latency: 824.346µs message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:13:10Z" - latency: 1.571319ms message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:12:10Z" - latency: 867.813µs message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:11:10Z" - latency: 807.258µs message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:10:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:37:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-170-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-170.ec2.internal uid: a28b465b-f1cb-4320-a128-5fa269918396 resourceVersion: "32603" uid: e7288e62-c7d6-4f19-a821-ff21db27b624 spec: sourcePod: network-check-source-8894fc9bd-5z9sm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T16:43:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.25572ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:19:10Z" - latency: 1.724935ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:19:10Z" - latency: 855.32µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:18:10Z" - latency: 1.843175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:18:10Z" - latency: 1.114793ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:17:10Z" - latency: 1.565895ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:17:10Z" - latency: 1.119477ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:16:10Z" - latency: 1.525565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:16:10Z" - latency: 1.158114ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:15:10Z" - latency: 1.494696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:15:10Z" kind: List metadata: resourceVersion: ""