apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "39095" uid: 6ac8800e-0720-49ca-b1f0-8c7a768e7313 spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:34:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.195806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 965.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:22:32Z" - latency: 998.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:21:32Z" - latency: 1.02894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:20:32Z" - latency: 834.001µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:19:32Z" - latency: 1.10837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:18:32Z" - latency: 1.064423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:17:32Z" - latency: 929.757µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:16:32Z" - latency: 891.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:15:32Z" - latency: 1.106086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "41251" uid: 462cc8da-60e5-45d1-afcd-f20b9f229cd4 spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:33:32Z" message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.49682ms message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:27:32Z" - latency: 8.199575ms message: 'load-balancer-api-external: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:27:32Z" - latency: 5.20042ms message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:26:32Z" - latency: 8.062675ms message: 'load-balancer-api-external: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:26:32Z" - latency: 5.785947ms message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:25:32Z" - latency: 7.189988ms message: 'load-balancer-api-external: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:25:32Z" - latency: 4.943985ms message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:24:32Z" - latency: 8.201269ms message: 'load-balancer-api-external: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:24:32Z" - latency: 5.131331ms message: 'load-balancer-api-external: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 7.864352ms message: 'load-balancer-api-external: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:23:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "41250" uid: 233ddf7f-f041-45e1-8cb7-6f9de0d514d5 spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:33:32Z" message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.513399ms message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:27:32Z" - latency: 8.106849ms message: 'load-balancer-api-internal: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:27:32Z" - latency: 5.213486ms message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:26:32Z" - latency: 8.016758ms message: 'load-balancer-api-internal: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:26:32Z" - latency: 5.157114ms message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:25:32Z" - latency: 7.176015ms message: 'load-balancer-api-internal: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:25:32Z" - latency: 4.555247ms message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:24:32Z" - latency: 8.130204ms message: 'load-balancer-api-internal: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:24:32Z" - latency: 5.114621ms message: 'load-balancer-api-internal: tcp connection to a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 7.911992ms message: 'load-balancer-api-internal: resolved host name a61ec1b7ee4da4875ae720f068e8fb9a-6904c3753617daa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:23:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-network-check-target-ip-10-0-130-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "39092" uid: f3968155-e00c-451f-8d52-4faa6c6fed3e spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:34:32Z" message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 805.815µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 811.616µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:22:32Z" - latency: 824.618µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:21:32Z" - latency: 1.450154ms message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:20:32Z" - latency: 1.303843ms message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:19:32Z" - latency: 882.08µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:18:32Z" - latency: 1.226225ms message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:17:32Z" - latency: 870.628µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:16:32Z" - latency: 946.631µs message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:15:32Z" - latency: 1.034915ms message: 'network-check-target-ip-10-0-130-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-network-check-target-ip-10-0-131-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "39094" uid: 80287758-350e-46e1-a2ae-af9c34d4cccd spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:34:32Z" message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.09199ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 2.429462ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:22:32Z" - latency: 2.12451ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:21:32Z" - latency: 2.586499ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:20:32Z" - latency: 2.062831ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:19:32Z" - latency: 2.117776ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:18:32Z" - latency: 2.152237ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:17:32Z" - latency: 2.046768ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:16:32Z" - latency: 2.201137ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:15:32Z" - latency: 2.078261ms message: 'network-check-target-ip-10-0-131-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-network-check-target-ip-10-0-140-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "39093" uid: fc6e5b3a-7e38-4558-863f-feb806909e89 spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:34:32Z" message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.64904ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 1.84872ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:22:32Z" - latency: 1.761734ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:21:32Z" - latency: 1.676046ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:20:32Z" - latency: 1.912238ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:19:32Z" - latency: 1.684579ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:18:32Z" - latency: 1.670151ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:17:32Z" - latency: 1.734506ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:16:32Z" - latency: 1.818472ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:15:32Z" - latency: 2.094553ms message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:27:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-17.ec2.internal uid: 9a337354-4f80-467d-ac20-1c622724137d resourceVersion: "41249" uid: 5e85ad00-6d95-456c-8566-f78d4231a323 spec: sourcePod: network-check-source-8894fc9bd-n6tvz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:33:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:27:32Z" - latency: 2.187953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:27:32Z" - latency: 856.81µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:26:32Z" - latency: 1.534181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:26:32Z" - latency: 1.069087ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:25:32Z" - latency: 1.649764ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:25:32Z" - latency: 961.218µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:24:32Z" - latency: 1.626692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:24:32Z" - latency: 889.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:23:32Z" - latency: 1.862962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:23:32Z" kind: List metadata: resourceVersion: ""