Add k3s-token and k3s-endpoint as output so other modules can re-use it. #946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
I'm currently building a terraform environment to add root-server to this cluster.
This is my current state of work: https://github.com/nupplaphil/terraform-root-kube-hetzner
Since I don't want to mix up root server and hcloud server, I choose a different repo for it.
The only thing missing is the "glue" between the hcloud terraform module and my root terraform module.
--> the k3s token and endpoint is missing.
With these two outputs, I was successfully to add a root-server to a cluster out of this project :)
btw the cilium config
doesn't work because XDP is incompatible with the vlan interface of the vSwitch subnet.
--> I manually overwrite the
cilium_values