Allow HA cluster setups about cluster-api-provider-digitalocean HOT 14 CLOSED

@xmudrii Is there an upstream issue for this? I tried to find one but didn't.

from cluster-api-provider-digitalocean.

@alvaroaleman Not that I'm aware of. Possibly we could create one in cluster-api repo.

from cluster-api-provider-digitalocean.

Does it belong there? Because at the end of the day the scripts that are responsible for creating a control plane (be it HA or not) live inside the providers or am I missing something here?

from cluster-api-provider-digitalocean.

To some degree. It would nice to make sure the proposed solution is okay with the Cluster-API team. Also, some changes to API could be required to ensure coordination between masters is possible.

I still have not researched a lot about this issues but I hope to get on it soon.

It may be even more relevant to cluster-api if we decide to upstream provisioning logic.

from cluster-api-provider-digitalocean.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from cluster-api-provider-digitalocean.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from cluster-api-provider-digitalocean.

This potentially could be handled at the provider level as well. It seems like there are some examples in the CAPI AWS provider.

/remove-lifecycle rotten

from cluster-api-provider-digitalocean.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from cluster-api-provider-digitalocean.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from cluster-api-provider-digitalocean.

/remove-lifecycle rotten

from cluster-api-provider-digitalocean.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from cluster-api-provider-digitalocean.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from cluster-api-provider-digitalocean.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

from cluster-api-provider-digitalocean.

@fejta-bot: Closing this issue.

from cluster-api-provider-digitalocean.