apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "18983" uid: 642ba3fb-fe31-42c5-b03c-f39c157e49a2 spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.342µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.028539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 1.035931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 1.029711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 1.015369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 1.061289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 874.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 908.033µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 951.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - latency: 884.974µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:08:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "21029" uid: d0d22511-fe51-4f70-ace6-c30e45492039 spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:09:31Z" message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.770024ms message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 8.254788ms message: 'load-balancer-api-external: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 5.054324ms message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 9.633872ms message: 'load-balancer-api-external: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 4.560286ms message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 7.901572ms message: 'load-balancer-api-external: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 5.205136ms message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 8.039473ms message: 'load-balancer-api-external: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" - latency: 5.478806ms message: 'load-balancer-api-external: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 11.900601ms message: 'load-balancer-api-external: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "21028" uid: e75c979a-71f7-422e-b894-159916437a13 spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:09:31Z" message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.748514ms message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 8.281368ms message: 'load-balancer-api-internal: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 5.040602ms message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 9.671755ms message: 'load-balancer-api-internal: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 4.611676ms message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 7.762831ms message: 'load-balancer-api-internal: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 5.190653ms message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 8.003214ms message: 'load-balancer-api-internal: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" - latency: 5.443675ms message: 'load-balancer-api-internal: tcp connection to aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 11.924625ms message: 'load-balancer-api-internal: resolved host name aacc1c600b3094b69adde4eae283482a-3d8846c253968f11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-network-check-target-ip-10-0-131-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "18981" uid: ed9def4d-6fa3-4592-9dbc-d794800c8c90 spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381534ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 2.35029ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 2.368065ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 2.236269ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 2.203537ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 2.25169ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.931676ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 2.193609ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 1.904282ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - latency: 2.166476ms message: 'network-check-target-ip-10-0-131-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:08:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-network-check-target-ip-10-0-136-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "18980" uid: 87d3a009-69a3-45cd-a62d-9d95579d5c83 spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.045222ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.899976ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 1.947527ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 2.193811ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 1.909586ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 1.922069ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.795902ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 1.645176ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 1.755049ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - latency: 1.863736ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:08:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-network-check-target-ip-10-0-141-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "18979" uid: 8ab4cd4c-14dc-4981-a2d8-36ecf5edc09d spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.328716ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.270611ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 847.021µs message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 863.66µs message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 700.32µs message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 1.339372ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.244108ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 685.992µs message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 1.130418ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - latency: 1.319799ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:08:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-131-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-131.ec2.internal uid: 5a7d7828-0702-42ae-aaee-474f03439e09 resourceVersion: "21027" uid: 05b5facc-d346-45b2-b00a-039870ae9eca spec: sourcePod: network-check-source-7b678d77c7-94g8p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:09:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 1.59605ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 751.033µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 2.038808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 754.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 1.651809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 946.377µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 1.736675ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" - latency: 834.82µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.600064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:17:31Z" kind: List metadata: resourceVersion: ""