apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "18043" uid: 7724dc5d-a078-4a7c-aa8f-8325a51c80ab spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T20:07:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.125306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:28Z" - latency: 1.078982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:28Z" - latency: 1.049351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 1.195167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 1.259684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 1.265182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 1.078465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 808.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:28Z" - latency: 1.12098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:28Z" - latency: 835.214µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "17054" uid: 9972affd-f0a5-4da5-9187-158c8a76bae6 spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:06:28Z" message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.935498ms message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 7.919523ms message: 'load-balancer-api-external: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:12:28Z" - latency: 5.442538ms message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 9.686562ms message: 'load-balancer-api-external: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:11:28Z" - latency: 4.96484ms message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 6.595459ms message: 'load-balancer-api-external: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:10:28Z" - latency: 4.74504ms message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 6.501404ms message: 'load-balancer-api-external: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:09:28Z" - latency: 4.959267ms message: 'load-balancer-api-external: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 7.196563ms message: 'load-balancer-api-external: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "17055" uid: f31fbf3f-bd3c-46ec-bdb8-e2bb6fdd309f spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:06:28Z" message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.828014ms message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 8.003572ms message: 'load-balancer-api-internal: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:12:28Z" - latency: 5.455969ms message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 9.777908ms message: 'load-balancer-api-internal: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:11:28Z" - latency: 4.79848ms message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 6.679036ms message: 'load-balancer-api-internal: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:10:28Z" - latency: 4.674132ms message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 6.705053ms message: 'load-balancer-api-internal: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:09:28Z" - latency: 4.916383ms message: 'load-balancer-api-internal: tcp connection to a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 7.235921ms message: 'load-balancer-api-internal: resolved host name a71408572e38b4d758a0d5857e303c5c-9ffa3badb8ab215a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-128-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "18042" uid: 6a889d3f-999e-44d6-8283-d868d4438124 spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:28Z" message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.343959ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:28Z" - latency: 1.913904ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:28Z" - latency: 1.744121ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 1.904363ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 1.79456ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 2.079612ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 1.890999ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 1.817417ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:28Z" - latency: 2.257827ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:28Z" - latency: 1.871705ms message: 'network-check-target-ip-10-0-128-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-131-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "18041" uid: 8f672c5a-325c-4e92-84b0-f0606763c041 spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:28Z" message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.727449ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:28Z" - latency: 1.865473ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:28Z" - latency: 2.014524ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 1.936789ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 1.756725ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 1.891948ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 1.936998ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 1.770395ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:28Z" - latency: 1.768604ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:28Z" - latency: 1.817831ms message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-135-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "18040" uid: d1b9f785-b148-4ef0-8174-e49f6fd332c1 spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:28Z" message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.417006ms message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:28Z" - latency: 870.014µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:28Z" - latency: 801.708µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 898.182µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 1.415764ms message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 958.232µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 808.85µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 865.651µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:28Z" - latency: 915.996µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:28Z" - latency: 962.065µs message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-72.ec2.internal uid: 9b896841-147b-4c28-865c-5739139d3dbb resourceVersion: "17053" uid: 615772e8-5295-4723-840b-772b3d415137 spec: sourcePod: network-check-source-8894fc9bd-f7ckn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T20:06:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056163ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:28Z" - latency: 1.749489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:12:28Z" - latency: 966.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:11:28Z" - latency: 1.845042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:11:28Z" - latency: 1.062606ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:10:28Z" - latency: 1.51905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:10:28Z" - latency: 970.321µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:09:28Z" - latency: 1.638141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:09:28Z" - latency: 837.186µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:28Z" - latency: 1.592451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:28Z" kind: List metadata: resourceVersion: ""