apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "21750" uid: bb55ce8d-9504-439e-839d-1e9e5bcf62b1 spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T14:21:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.078295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:35:01Z" - latency: 1.472377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:34:01Z" - latency: 956.131µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:33:01Z" - latency: 991.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 1.002914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 1.142347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 1.082303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 1.971776ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 890.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:27:01Z" - latency: 874.172µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:26:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "20420" uid: d6bb84cb-f6a4-408d-bcaf-24abb01b92dc spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:20:01Z" message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.172082ms message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 13.019989ms message: 'load-balancer-api-external: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:32:01Z" - latency: 5.743058ms message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 8.277579ms message: 'load-balancer-api-external: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:31:01Z" - latency: 8.651244ms message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 9.840019ms message: 'load-balancer-api-external: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:30:01Z" - latency: 5.749197ms message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 10.266556ms message: 'load-balancer-api-external: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:29:01Z" - latency: 7.611452ms message: 'load-balancer-api-external: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 12.980446ms message: 'load-balancer-api-external: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "20421" uid: 8ff48438-ce86-4cd7-83a2-7b13d44e734a spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:20:01Z" message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.958972ms message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 12.977248ms message: 'load-balancer-api-internal: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:32:01Z" - latency: 5.751634ms message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 8.342296ms message: 'load-balancer-api-internal: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:31:01Z" - latency: 5.485968ms message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 9.820192ms message: 'load-balancer-api-internal: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:30:01Z" - latency: 5.743589ms message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 10.360962ms message: 'load-balancer-api-internal: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:29:01Z" - latency: 7.246468ms message: 'load-balancer-api-internal: tcp connection to afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 13.062611ms message: 'load-balancer-api-internal: resolved host name afad02d262e4d4801919da351ea09c33-97fcc3da1c498268.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-network-check-target-ip-10-0-130-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "21752" uid: 4ac03936-1e8c-4d6c-8d81-d3d10dc96ee1 spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:21:01Z" message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.317092ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:35:01Z" - latency: 2.148724ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:34:01Z" - latency: 2.254932ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:33:01Z" - latency: 2.09782ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 2.08975ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 2.329898ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 2.248557ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 3.166635ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 1.749882ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:27:01Z" - latency: 2.148063ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:26:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-network-check-target-ip-10-0-135-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "21751" uid: 2cb5a30f-925c-4e88-8bf8-b26875528709 spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:21:01Z" message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.433073ms message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:35:01Z" - latency: 1.548678ms message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:34:01Z" - latency: 970.72µs message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:33:01Z" - latency: 901.085µs message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 1.118326ms message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 891.464µs message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 900.356µs message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 1.86401ms message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 837.01µs message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:27:01Z" - latency: 1.099845ms message: 'network-check-target-ip-10-0-135-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:26:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-network-check-target-ip-10-0-138-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "21749" uid: 9ac8b941-bdaa-4a7d-a7e3-d875fa9ff375 spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:21:01Z" message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.087173ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:35:01Z" - latency: 2.112582ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:34:01Z" - latency: 2.068095ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:33:01Z" - latency: 1.889103ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 1.905098ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 1.980034ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 1.913483ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 2.6757ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 1.728036ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:27:01Z" - latency: 1.884846ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:26:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:13:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-29-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-29.ec2.internal uid: f5256c00-0188-4e98-884e-62f20f88c87b resourceVersion: "20419" uid: cab8c2db-2371-4cea-bd60-2720ee71c4f9 spec: sourcePod: network-check-source-989f8b8dc-p5d4q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T14:20:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017699ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:32:01Z" - latency: 1.850226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:32:01Z" - latency: 865.374µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:31:01Z" - latency: 1.692379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:31:01Z" - latency: 896.236µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:30:01Z" - latency: 1.798775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:30:01Z" - latency: 776.096µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:29:01Z" - latency: 1.805611ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:29:01Z" - latency: 942.171µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:28:01Z" - latency: 2.977023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:28:01Z" kind: List metadata: resourceVersion: ""