3 ms·

Features like this feel like table stakes for cloud hosting in 2017, so it's nice to see DigitalOcean on board. It'll be interesting to see what the tooling su

Features like this feel like table stakes for cloud hosting in 2017, so it's nice to see DigitalOcean on board. It'll be interesting to see what the tooling support looks like for this, it looks like it's launching with API support day one: https://developers.digitalocean.com/documentation/v2/ https://developers.digitalocean.com/documentation/v2/ which is great. It looks like they're already working to get it into Terraform: https://github.com/hashicorp/terraform/pull/15121 https://github.com/hashicorp/terraform/pull/15121 which is fantastic! I look forward to the day that I can automatically spin up a DigitalOcean set of Droplets running Kubernetes using this.

tyingq 9y ago
>I look forward to the day that I can automatically spin up a DigitalOcean set of Droplets running Kubernetes using this Stackpoint.io can do this, you paste your DO API key and get a k8s cluster in a few minutes. Would be nice if DO built something like that in-house.
- skrebbel 9y ago
  > Would be nice if DO built something like that in-house. Curious, why? Isn't it much nicer to keep that separate from DO so that you can move away from DO easily should there be a reason to? I'm not sure if I'm weird this way, but one main reason we use DO and not, say, AWS is because we're afraid of vendor lock-in. The more we depend on specialized services, the harder it gets to move somewhere. I wonder whether this is a common sentiment in 2017 or whether I'm just old-fashioned.
  - tyingq 9y ago
    Hosted K8s isn't much lock-in...you could move to GKE or Azure.