New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor to not use Kubernetes provider. #40

Closed

errm opened this issue Feb 26, 2020 · 0 comments · Fixed by #41

Member

errm commented Feb 26, 2020

I have come to the conclusion that using the Kubernetes Provider to bootstrap the cluster is sub-optimal for some reasons:

It's a bit overkill - we don't really need terraform to manage the full lifecycle of Kubernetes objects (it can do that itself)
Lazy config of the Kubernetes provider isn't recommended (and was broken by the latest version Provider 1.11.0 fails to initialize hashicorp/terraform-provider-kubernetes#759) https://xkcd.com/1172/
There is a mismatch between terraform config and yaml that makes it harder to diff from upstream...

errm added a commit that referenced this issue


          Remove kubernetes provider

073f694

Refactor to use dumb kubectl apply!

Fixes #40

errm mentioned this issue

Remove kubernetes provider #41

Merged

errm closed this as completed in #41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment