Skip to content
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.

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

Upgrade terraform-provider-ct to v0.3.0 #296

Closed
nikolay opened this issue Sep 17, 2018 · 8 comments
Closed

Upgrade terraform-provider-ct to v0.3.0 #296

nikolay opened this issue Sep 17, 2018 · 8 comments

Comments

@nikolay
Copy link

nikolay commented Sep 17, 2018

https://github.com/coreos/terraform-provider-ct/releases/tag/v0.3.0

@dghubble
Copy link
Member

Be warned: #275

@nikolay
Copy link
Author

nikolay commented Sep 19, 2018

@dghubble Isn't v0.3.0 though the way to go for new clusters and infrastructure, which won't have the old schema? Anyway, it seems that my cluster gets stuck if I deploy using v0.3.0 anyway.

@elemental-lf
Copy link
Contributor

@nikolay, didn't work for me either. Installations wouldn't complete successfully. Didn't really investigate at that time, so this is little more than a "me too".

@nikolay
Copy link
Author

nikolay commented Sep 21, 2018

Honestly, I'm not sure why this is needed as Terraform has a standard ignition provider, which Tectonic Installer is using. The whole setup will be trimmed down if Typhoon switches to it. It supports 2.1.0 though, not 2.2.0, but differences are minor. I already submitted a ticket (hashicorp/terraform-provider-ignition#42), but I have the feeling that this provider is, pretty much, not maintained.

@dghubble
Copy link
Member

The Container Linux Config YAML format was designed for human readability and committing to source control. The tools we wrote at CoreOS, ct and terraform-provider-ct transpile to Ignition JSON. I'm well aware of terraform-provider-ct and I'll not be switching to it.

Terraform should not be about reimplementing every description language in HCL. The focus here is to use it only for infrastructure resources.

Leaving this open for when I get around to v0.3.0.

@dghubble
Copy link
Member

Once all managed clusters are on v1.12.2, you may safely update the terraform-provider-ct plugin without affecting controller nodes (I've tried it on every platform). After v1.12.2, the docs can be updated to point readers to new terraform-provider-ct versions.

@dghubble
Copy link
Member

Migration docs for switching to the 3rd-party plugin directory https://github.com/poseidon/typhoon/pull/349/files#diff-5820b1d0cffba936ed0da1057f3a6140 Once that's complete, v1.12.2+ clusters can update to newer versions of the terraform-provider-ct plugin.

@dghubble
Copy link
Member

Going forward, guides use terraform-provider-ct v0.3.0. There is also a migration guide to upgrade the plugin in-place for v1.12.2+ clusters. https://typhoon.psdn.io/topics/maintenance/#upgrade-terraform-provider-ct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants