Background

KCM and KAS previously relied on having the `{}cloud-provider` and `{-}-cloud-config` flags set. However, these are no longer required as there is no cloud provider code in either binary.

Both operators rely on the config observer in library go to set these flags.

In the future, if these values are set, even to the empty string, then startup will fail.

The config observer sets keys and values for a map (see), we need to make sure the keys for these two flags are deleted rather than set to a specific value.

Steps

• Update the logic in the config observer to remove the `{}cloud-config` and `{-}-cloud-provider` flag, neither should be set going forward
• Update KAS and KCM operators to include the new logic.

Stakeholders

• Cluster Infra
• API team
• Workloads team

Definition of Done

• Clusters do not set `{}cloud-provider` or `{-}-cloud-config` on KAS and KCM

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>