Proposal: Implement the cluster-api-do controller for handling DigitalOcean Kubernetes clusters #211
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
k8s-ci-robot
added
the
kind/feature
|
Dupe of #55? |
6 tasks
chuckha
pushed a commit
to chuckha/cluster-api
that referenced
this issue
Oct 2, 2019
🐛 Test and logic fixes
jayunit100
pushed a commit
to jayunit100/cluster-api
that referenced
this issue
Jan 31, 2020
) Updates the create workflow to also look for the created VM using the instance UUID before triggering the clone operation. This would avoid the system to go into a recursive clone operation in case the update for the first clone task is missed somehow. The updated create workflow would look like: https://tinyurl.com/y5u8lpjl Added the create workflow diagram under design folder Change-Id: I91810168193d1f2ca6002233e84f42a994917077
fxierh
pushed a commit
to fxierh/cluster-api
that referenced
this issue
Sep 14, 2024
…te-owners NO-JIRA: Update OWNERS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type: Proposal
It would be nice to have a controller, like for AWS/GCP, for handling cluster creation and managing DigitalOcean Droplets (instances).
I'm willing to work and maintain this one if there is interests for such controller. Let me know is there something else needed to be provided for a proposal.
/kind feature
/cc @kris-nova
The text was updated successfully, but these errors were encountered: