✨ [VC] Support Auto Reloading KUBECONFIGs from Secrets

[christopherhein]

User Story

As a operator I would like the syncer to auto reload changes to KUBECONFIG secrets so that the syncer can stay up to date with PKI expiry w/o intervention.

Detailed Description

In the next version of VC w/ CAPN/CAPI Support control planes are being provisioned out of cluster and linked via two annotations, along w/ the old path for native provisioning would load the KUBECONFIG bytes once then never reload unless the syncer is restarted. This happens here - https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/pkg/syncer/conversion/helper.go#L84-L99

With the new CAPI/CAPN support this lifecycle should be automated so if CAPI expires the KUBECONFIG credentials (every 6months) that they syncer reloads the client.

Anything else you would like to add:

Hold until #81 is done.

/kind feature /milestone v0.1.x

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[christopherhein]

/remove-lifecycle stale /lifecycle frozen