3 ms·
The Terraform provider idea is interesting, I'll think about it more carefully. Almost all of our deployment configuration under the hood is done with Kubernete
by ospillinger 7y ago
The Terraform provider idea is interesting, I'll think about it more carefully. Almost all of our deployment configuration under the hood is done with Kubernetes (which is focused on the declaration of deployment state). We modeled our configuration after Kubernetes for that reason, and we want to go beyond low-level infrastructure configuration by allowing users to configure prediction tracking, model retraining thresholds, and other more ML specific features using the same declarative paradigm and in the same configuration files.
- sandGorgon 7y agoTerraform has first class support for K8s - https://www.terraform.io/docs/providers/kubernetes/index.html https://www.terraform.io/docs/providers/kubernetes/index.htm... In fact, i would say that's what Terraform was built around, so there's nothing more maintained than the k8s provider. In addition, it has EKS (https://www.terraform.io/docs/providers/aws/r/eks_cluster.html https://www.terraform.io/docs/providers/aws/r/eks_cluster.ht...) as well as GKE providers (https://www.terraform.io/docs/providers/google/r/container_cluster.html https://www.terraform.io/docs/providers/google/r/container_c...) in case you are so inclined.
- dankohn1 7y agoTerraform slightly predates Kubernetes, May 21 vs. June 6, 2014. They were developed independently. Links at: https://landscape.cncf.io/category=automation-configuration,scheduling-orchestration&format=card-mode&grouping=no&organization=cloud-native-computing-foundation-cncf,hashi-corp&sort=first-commit https://landscape.cncf.io/category=automation-configuration,...