apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46362" uid: 05b0c46f-2f5b-4e2f-b549-2a3f7f4cc530 spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:04:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.721µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 934.909µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 1.16825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 1.067255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 1.360301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 1.302712ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:49Z" - latency: 895.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:49Z" - latency: 1.152882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:49Z" - latency: 952.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:49Z" - latency: 1.018517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46364" uid: 8700f7d5-895c-4d34-b370-2bdb48826a59 spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:03:49Z" message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.130956ms message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 7.456897ms message: 'load-balancer-api-external: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:21:49Z" - latency: 7.39162ms message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 6.167032ms message: 'load-balancer-api-external: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:20:49Z" - latency: 5.233295ms message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 6.519263ms message: 'load-balancer-api-external: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:49Z" - latency: 7.244027ms message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 6.375988ms message: 'load-balancer-api-external: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:49Z" - latency: 4.701865ms message: 'load-balancer-api-external: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 7.1671ms message: 'load-balancer-api-external: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46363" uid: 5e4bf982-80c2-49d0-a84b-0a71838a65ce spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:03:49Z" message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.11545ms message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 7.497945ms message: 'load-balancer-api-internal: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:21:49Z" - latency: 5.360726ms message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 6.090209ms message: 'load-balancer-api-internal: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:20:49Z" - latency: 5.233594ms message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 6.570184ms message: 'load-balancer-api-internal: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:49Z" - latency: 6.451644ms message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 6.407353ms message: 'load-balancer-api-internal: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:49Z" - latency: 4.760349ms message: 'load-balancer-api-internal: tcp connection to a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 7.219302ms message: 'load-balancer-api-internal: resolved host name a1bf10caf35a343cf8ade7e7950838da-5faa5e806963b3f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-network-check-target-ip-10-0-132-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46359" uid: bede0014-7e5f-486e-bdb8-ad76bb983f80 spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:04:49Z" message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.991715ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 1.78324ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 2.221267ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 2.222688ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 2.033695ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 2.44612ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:49Z" - latency: 2.134727ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:49Z" - latency: 2.268341ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:49Z" - latency: 2.119082ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:49Z" - latency: 2.312936ms message: 'network-check-target-ip-10-0-132-106: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-network-check-target-ip-10-0-132-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46358" uid: 979f9543-7b74-4e36-9a09-ccc297691f3f spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:04:49Z" message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 900.388µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 1.353095ms message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 906.443µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 1.453598ms message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 1.553441ms message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 950.641µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:49Z" - latency: 983.968µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:49Z" - latency: 897.644µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:49Z" - latency: 996.151µs message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:49Z" - latency: 1.255655ms message: 'network-check-target-ip-10-0-132-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-network-check-target-ip-10-0-135-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46360" uid: d4e2b57a-a4c8-464d-8c29-223161b7533a spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:04:49Z" message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266125ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 2.277626ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 2.160351ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 2.204922ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 2.110299ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 2.395421ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:49Z" - latency: 2.528036ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:49Z" - latency: 2.164855ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:49Z" - latency: 2.038561ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:49Z" - latency: 2.207244ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-24.ec2.internal uid: c065fc2c-be75-4a6e-ac1f-8ab6e13ea523 resourceVersion: "46361" uid: 48317db2-9bc4-4754-93bc-5a31f041d786 spec: sourcePod: network-check-source-8894fc9bd-5t9k8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:03:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.172µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:21:49Z" - latency: 2.206794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:21:49Z" - latency: 1.054429ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:20:49Z" - latency: 1.828823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:20:49Z" - latency: 836.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:49Z" - latency: 1.825552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:49Z" - latency: 759.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:49Z" - latency: 1.530771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:49Z" - latency: 1.020637ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:49Z" - latency: 2.011982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:49Z" kind: List metadata: resourceVersion: ""