apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "43846" uid: 7ae1192d-0b73-4508-a188-138e1eb665c3 spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T01:21:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 800.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 1.191036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 729.631µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:39:11Z" - latency: 1.004201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:38:11Z" - latency: 1.119209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:37:11Z" - latency: 1.014533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:36:11Z" - latency: 1.266598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:35:11Z" - latency: 870.884µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:34:11Z" - latency: 1.009233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:33:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "46041" uid: 45132adc-5269-47b4-a27c-700a71978e06 spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T01:20:11Z" message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.24833ms message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:44:11Z" - latency: 7.225207ms message: 'load-balancer-api-external: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:44:11Z" - latency: 4.071134ms message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:43:11Z" - latency: 6.948352ms message: 'load-balancer-api-external: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:43:11Z" - latency: 3.753467ms message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 7.604972ms message: 'load-balancer-api-external: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:42:11Z" - latency: 5.282139ms message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 6.298688ms message: 'load-balancer-api-external: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:41:11Z" - latency: 5.900446ms message: 'load-balancer-api-external: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 8.019812ms message: 'load-balancer-api-external: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:40:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "46040" uid: 57249c44-82c3-410c-b417-0f76401f1df1 spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T01:20:11Z" message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.222149ms message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:44:11Z" - latency: 7.372087ms message: 'load-balancer-api-internal: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:44:11Z" - latency: 4.638168ms message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:43:11Z" - latency: 7.016109ms message: 'load-balancer-api-internal: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:43:11Z" - latency: 3.65618ms message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 7.696617ms message: 'load-balancer-api-internal: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:42:11Z" - latency: 5.382702ms message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 6.263062ms message: 'load-balancer-api-internal: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:41:11Z" - latency: 5.904974ms message: 'load-balancer-api-internal: tcp connection to ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 7.970371ms message: 'load-balancer-api-internal: resolved host name ae7927e942da24e719bf1a5b0318cb29-9114f0b7f48cff7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T01:40:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-network-check-target-ip-10-0-135-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "43843" uid: 1fe0ef09-2a06-43f7-b34f-4c5d9211259c spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T01:21:11Z" message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.446µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 844.395µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 767.918µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 1.45515ms message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:39:11Z" - latency: 866.9µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:38:11Z" - latency: 895.236µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:37:11Z" - latency: 935.151µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:36:11Z" - latency: 875.188µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:35:11Z" - latency: 1.355696ms message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:34:11Z" - latency: 918.074µs message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:33:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-network-check-target-ip-10-0-137-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "43845" uid: 07bf3ed1-9a8c-4ecd-82e1-27afd538b69e spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T01:21:11Z" message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13905ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 2.163261ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 2.558799ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 1.96741ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:39:11Z" - latency: 2.460827ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:38:11Z" - latency: 2.413097ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:37:11Z" - latency: 1.961216ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:36:11Z" - latency: 1.976687ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:35:11Z" - latency: 2.206792ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:34:11Z" - latency: 2.082431ms message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:33:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-network-check-target-ip-10-0-138-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "43844" uid: 3f0fcf1c-ab86-4f8a-a0d5-9a403dd6b64c spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T01:21:11Z" message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.820721ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 1.806921ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 2.196607ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 1.637995ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:39:11Z" - latency: 2.143263ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:38:11Z" - latency: 2.157183ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:37:11Z" - latency: 1.85512ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:36:11Z" - latency: 1.957085ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:35:11Z" - latency: 1.943927ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:34:11Z" - latency: 1.950876ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:33:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T01:14:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-74.ec2.internal uid: 8c627685-5396-4a35-b137-b5ed5f4e00d8 resourceVersion: "46039" uid: b3e166a7-51a0-4e61-afd8-6c62110eee2a spec: sourcePod: network-check-source-8894fc9bd-d2wkz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T01:20:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.03232ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:44:11Z" - latency: 1.755376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T01:44:11Z" - latency: 780.59µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:43:11Z" - latency: 2.148055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T01:43:11Z" - latency: 915.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:42:11Z" - latency: 1.767106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T01:42:11Z" - latency: 994.88µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:41:11Z" - latency: 1.702098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T01:41:11Z" - latency: 808.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T01:40:11Z" - latency: 2.366992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T01:40:11Z" kind: List metadata: resourceVersion: ""