Support disabling bastion host

[simonklb]

/kind feature

Describe the solution you'd like

Currently, disabling a bastion host is not allowed after it has been enabled. Instead you have to tear down the entire cluster to remove it. I would like to be able to disable the bastion host while keeping the cluster alive.

Anything else you would like to add:

Support for enabling a bastion host was added in https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/1300. There it was decided that disabling the bastion once it had been enabled would not be allowed due to the lack of support for garbage collecting it. However a follow-up ticket was proposed to implement this in this Slack thread but I've not been able to find it when searching the issues here. Please close this as a duplicate if it already exist!

[dtzar]

This is not a duplicate, but this isn't on our priority list as you're the first person I know of to ask for it (aside from that slack request 3 years ago). PRs are welcome!

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale