solve proxy issue for capd+rke2 deployment

Sakshi Choudharyrequested to merge
version-test into main

What does this MR do and why?

This MR fixes the proxy issue which was faced while deploying rke2controlplane in capd

Related reference(s)

Closes issue -- #1244 (closed)

Test coverage

I deployed rke2 capd with my dev branch and it was successful

 ✓ Kustomization/sylva-system/management-namespace-defs - Resource is ready
 ✓ Kustomization/sylva-system/management-sylva-units - Resource is ready
 ✓ Kustomization/sylva-system/namespace-defs - Resource is ready
 ✓ Kustomization/sylva-system/pivot - Resource is ready
 ✓ Kustomization/sylva-system/sylva-units-status - Resource is ready
 ✓ All Done!

also deployed kubeadm capd deployment and it was successful everything is working fine

✓ Kustomization/flux-webui - Resource is ready: Flux Web UI can be reached at https://flux.sylva (flux.sylva must resolve to 172.18.0.100)
✓ Kustomization/harbor-init - Resource is ready
✓ Kustomization/harbor-postgres - Resource is ready
✓ Kustomization/harbor - Resource is ready: Harbor UI can be reached at https://harbor.sylva (harbor.sylva must resolve to 172.18.0.100)
⠈⠁ Kustomization/sylva-units-status -
✓ All Done: resource Kustomization/sylva-system/sylva-units-status is ready!
✔ Sylva is ready, everything deployed in management cluster

Management cluster nodes:
NAME                                     STATUS   ROLES           AGE   VERSION
management-cluster-control-plane-vg2tg   Ready    control-plane   33m   v1.28.7
Edited by Sakshi Choudhary

Merge request reports