❓ Investigate v1alpha5 CAPI changes around EtcdProvider

[christopherhein]

User Story

As a operator I would like to use an external etcd provider so that I can run more HA etcd clusters not stacked.

Detailed Description

We should evaluate what impact this will have with CAPN currently and what it might effect with regards to #44

Anything else you would like to add:

Xref: kubernetes-sigs/cluster-api#4659

/kind feature
/milestone next

[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