Fix no_proxy drift in RKE2ControlPlane during Minsiserve installation

Ishita Mittalrequested to merge
ishita/set-no-proxy-miniserve into main

When working on sylva-projects/sylva-core!4758 (merged), I found that during Minsiserve server installation, exporting no_proxy can introduce additional values (including kind cluster pods/services subnets) from the bootstrap cluster. These values are not present in the RKE2ControlPlane resource in the management cluster, which causes Flux to detect a drift. When Flux corrects this drift, it also triggers unnecessary node rolling updates.

This MR fixes it by ensuring that exporting no_proxy during Minsiserve installation does not create differences in the RKE2ControlPlane resource and also prevents unnecessary drifts and rolling updates.

Edited by Ishita Mittal

Merge request reports