Let’s Encrypt, OAuth 2, and Kubernetes Ingress

Re:Let’s Encrypt, OAuth 2, and Kubernetes Ingress by agentgt on Wednesday February 22, 2017 @09:44AM (#13705819)

Question for the author: We just migrated some stuff to GCP as well but do not use kubernetes. For managing infrasructure we only use packer, bash, and google cloud deployment yaml files (similar to the kubernetes manifest).

Why do you still need saltstack and how do you find terraform? Why do you need terraform (I suppose it is for your non kubernetes infrastructure?)?

[ Parent | on HN ]

Re:Let’s Encrypt, OAuth 2, and Kubernetes Ingress by fortytw2 on Wednesday February 22, 2017 @09:49AM (#13705867)

For the moment at least, it's much more comfortable for us to keep our databases outside of kubernetes, so we use saltstack(masterless), packer, and terraform to manage them. We also use terraform to manage all of our DNS, which is split between Route53 and the GCP DNS service.

[ Parent | on HN ]

Re:Let’s Encrypt, OAuth 2, and Kubernetes Ingress by agentgt on Wednesday February 22, 2017 @10:01AM (#13705966)

Thanks! I have been meaning to give terraform a try to replace some of our custom gcloud + gcloud deployment descriptors. Also so that we don't need a separate docker compose version for development (I'm assuming in theory you can run terraform to do what docker compose does?).

[ Parent | on HN ]

Re:Let’s Encrypt, OAuth 2, and Kubernetes Ingress by morgante on Wednesday February 22, 2017 @10:35AM (#13706227)

> Also so that we don't need a separate docker compose version for development (I'm assuming in theory you can run terraform to do what docker compose does?).

Not really. Terraform is much more meant as a tool for manipulating production infrastructure (primarily clouds), not for orchestrating Docker containers (including locally).

I'd strongly recommend you use the right tool for the job and it's a very rare job where Terraform is a good alternative to docker-compose.

[ Parent | on HN ]