Refactoring to become more terraformic #1554
janfrederik
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Going through the code, I see most of the magic is done using provisioners (file, remote-exec, ...). Following the terraform mindset (and documentation), these constructs should only be used as a last resort.
Is there a reason?
At first sight, it seems to me that at least everything that is installed inside kubernetes (once the first control plane is up), could be created and configured using official and/or widespread used providers, like the kubernetes, helm, kubectl or kustomization providers. This would make the resource lifecycle if not more reliable, then at least more clear.
Beta Was this translation helpful? Give feedback.
All reactions