apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "18589" uid: 9d77bcbe-59d1-45be-a051-921738b1f86f spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T19:17:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 1.034727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:23:51Z" - latency: 1.087956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:22:51Z" - latency: 811.647µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:21:51Z" - latency: 931.345µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:20:51Z" - latency: 1.107357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:19:51Z" - latency: 929.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:18:51Z" - latency: 1.016648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:17:51Z" - latency: 1.284109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:16:51Z" - latency: 1.078818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:15:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "20716" uid: ef4ab9db-8606-4ff7-97f8-281571896ab1 spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:16:51Z" message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.761669ms message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:28:51Z" - latency: 12.651252ms message: 'load-balancer-api-external: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:28:51Z" - latency: 5.737238ms message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:27:51Z" - latency: 14.216013ms message: 'load-balancer-api-external: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:27:51Z" - latency: 5.339941ms message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:26:51Z" - latency: 10.983832ms message: 'load-balancer-api-external: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:26:51Z" - latency: 3.473636ms message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:25:51Z" - latency: 11.718238ms message: 'load-balancer-api-external: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:25:51Z" - latency: 4.501437ms message: 'load-balancer-api-external: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 11.938841ms message: 'load-balancer-api-external: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:24:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "20715" uid: b643ea32-1e91-4375-8576-514cbc2a97cb spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:16:51Z" message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.786148ms message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:28:51Z" - latency: 12.690094ms message: 'load-balancer-api-internal: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:28:51Z" - latency: 5.726211ms message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:27:51Z" - latency: 14.18291ms message: 'load-balancer-api-internal: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:27:51Z" - latency: 5.297278ms message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:26:51Z" - latency: 11.01749ms message: 'load-balancer-api-internal: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:26:51Z" - latency: 3.285674ms message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:25:51Z" - latency: 11.75263ms message: 'load-balancer-api-internal: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:25:51Z" - latency: 3.618935ms message: 'load-balancer-api-internal: tcp connection to a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 11.984114ms message: 'load-balancer-api-internal: resolved host name a1d0ef737d7a845b488414d30ad4ca60-b2f478bf34112e4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:24:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-137-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "18587" uid: 8150c89c-23fd-479a-a2c4-fd5c90e20336 spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:17:51Z" message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.876939ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 1.899533ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:23:51Z" - latency: 1.897124ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:22:51Z" - latency: 1.752541ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:21:51Z" - latency: 1.922336ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:20:51Z" - latency: 1.99702ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:19:51Z" - latency: 1.852381ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:18:51Z" - latency: 1.714664ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:17:51Z" - latency: 1.923309ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:16:51Z" - latency: 2.069873ms message: 'network-check-target-ip-10-0-137-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:15:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "18588" uid: dd77b113-1b29-4d0f-b04b-36fc78461761 spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:17:51Z" message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.236338ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 2.102752ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:23:51Z" - latency: 2.116196ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:22:51Z" - latency: 2.157527ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:21:51Z" - latency: 2.059043ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:20:51Z" - latency: 2.13905ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:19:51Z" - latency: 2.032347ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:18:51Z" - latency: 2.137461ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:17:51Z" - latency: 2.17035ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:16:51Z" - latency: 2.098273ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:15:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "18586" uid: 8673df37-fd07-4325-9871-9bf0047d2149 spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:17:51Z" message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.829µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 1.058506ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:23:51Z" - latency: 855.71µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:22:51Z" - latency: 986.053µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:21:51Z" - latency: 1.203443ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:20:51Z" - latency: 1.464109ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:19:51Z" - latency: 1.313323ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:18:51Z" - latency: 1.238469ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:17:51Z" - latency: 919.392µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:16:51Z" - latency: 1.11266ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:15:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 09a8146b-32de-41ea-951c-294d9e856813 resourceVersion: "20713" uid: b905f9a1-94c0-4bf8-aab8-67920d413b50 spec: sourcePod: network-check-source-8894fc9bd-6gmp9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T19:16:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.973µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:28:51Z" - latency: 1.952239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:28:51Z" - latency: 874.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:27:51Z" - latency: 1.635836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:27:51Z" - latency: 989.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:26:51Z" - latency: 1.761173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:26:51Z" - latency: 836.144µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:25:51Z" - latency: 1.843938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:25:51Z" - latency: 964.576µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:24:51Z" - latency: 1.797359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:24:51Z" kind: List metadata: resourceVersion: ""