3 ms·
And with terraform, you're going to be writing pretty much from scratch with every provider out there, as outside of very basics of infrastructure the offerings
by p_l 5y ago
And with terraform, you're going to be writing pretty much from scratch with every provider out there, as outside of very basics of infrastructure the offerings differ wildly, and even if all you need is a VM with dumb load balancer you have to write ~5x$CLOUD_PROVIDERS resources and abstract it around.
Personally k8s is least interesting in scaling, because you could easily scale with other options if you had money to burn
- jeltz 5y agoThe same is true for Kubernetes too from my experience. Only the very basics of it works cross provider.
- p_l 5y agoThing is, nothing in Terraform works cross-provider - it's just a (often clunky, though it got better) DSL over JSON which makes for nicer way to call vendor APIs. But I need to know all the details of those APIs anyway. With K8s, the basics that "just work" are pretty wide, the bits that are specific to vendor that are necessary are usually small and contained, and for everything else I have extensible API that allows abstractions like crossplane.io
- eof 5y agoecosystem is changing rapidly. i actually couldn't say if this is true as I have not played with any of the hosted k8s environments outside of highly complex real world usage. it does seem completely plausible that within the last year or so hosted environments are stable enough and standardized enough that k8s can be a target directly even for small projects. cool. i will try for my next one
- p_l 5y agoThe state I described above was somewhat solid by early 2017. Biggest possible issues were if you wanted to pass things like cloud credentials to your apps etc., but standard k8s resources worked pretty well with at most some extra annotations to for example link a Service of type LoadBalancer with specific pre-allocated IP.