Terraform Provider for RKE2 (terraform-provider-rke2)

[ondrejsika]

I'm using RKE with terraform-provider-rke and I love it. It would be great to have a Terraform provider for RKE2.

[vojtechmares]

I would love to have a Terraform provider for RKE2. I am using RKE1's provider to manage all my clusters and I would like to migrate to RKE2, but this is for me a deal breaker atm. Thanks!

[stefandanaita]

Same, it would be great to have an rke2 terraform provider :(

[janlauber]

Same for me, please add this request to your roadmap.

[l-with]

I think, it is essential to have a terraform provider for rke2. Please implement.

[erSitzt]

Any news on this ? Is there anything planned or in the works ?

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

[erSitzt]

still want to know :)

[Martin-Weiss]

We have the terraform provider for Rancher that supports provisioning RKE2 downstream clusters.
https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster_v2
Wouldn’t that do the job?

[erSitzt]

@Martin-Weiss yes that would do the job... but we handle additional resources like additional/later changes to the machines, loadbalancers and dns entries via terraform/ansible and last time i checked it didnt look like it was possible to get the ips of the the nodes from the different pools/machines created ? (maybe in a hacky way but not directly ? )

The other thing i didnt like about using the the cluster resource is the assignment of ip addresses. I dont want to use dhcp because of reasons, but instead assign ranges which is easy in terraform... not so much via the rancher provider.

This is all on-prem and i have a good working setup... the only part that is a little hacky is the rke2 install part.
And as there were multiple statements that an rke2 provider is in the works i just wanted to know if there is indeed something coming...

Correct me if i'm wrong somewhere... i dont need the rke2 provider, but there never was a definitive answer if its coming or not...

[Martin-Weiss]

@erSitzt - I am using the Rancher terraform provider to deploy RKE2 on premise and I am also using static IP addresses for the machines (my way is to use one machine-pool per machine and use specific cloud-init data with it). I believe there is also a way to get the IPs later from the machine pool but have not used that one myself.
I can not say if there will be a separate rke2 provider but I assume the strategy is via rancher2...

[erSitzt]

That's sounds a little hacky as well 😊
I'm okay with my current deployment.. it's a modified version of DavidVTUKs examples.

But still, it would be nice to know if there won't be a rke2 provider...

[rahendatri]

Hello,

+1 for this issue.
My team need to manage several Rancher/RKE2 instances.

Suggested hack here (#1676 (comment)) will not fit our use case because it requires having an already popped Rancher instance.

Instead, we need to create RKE2 resources and then Rancher resources. Having an RKE2 provider will allow stateful management of Rancher on RKE2.

[caroline-suse-rancher]

For those still interested, work is being planned for a standalone RKE2 terraform module and will be tracked in #4322 :) I'll be closing this issue in favor of that one.