You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my clusters I have only the api server on the control plane nodes exposed to my management workstation so I always use the cluster endpoint for talosctl et.al.
Using talosctl this works (10.0.0.6 is the internal ip of the worker node):
endpoint.my-cluster.com points to the control plane nodes via round-robin dns. If I use that instead of cp[0] in terraform the config gets applied to a random control plane node.
Using the internal or external ip of the worker node in terraform does not make a difference. Where the config gets applied depends solely on the endpoint selected.
Environment
Provider version: 0.1.0-alpha.9
The text was updated successfully, but these errors were encountered:
Bug Report
This looks very similar to #17 though the resource has been reworked since.
Description
The following will apply the new configuration to the first control plane node instead of worker 1:
The following works as expected:
Background
In my clusters I have only the api server on the control plane nodes exposed to my management workstation so I always use the cluster endpoint for talosctl et.al.
Using talosctl this works (10.0.0.6 is the internal ip of the worker node):
endpoint.my-cluster.com
points to the control plane nodes via round-robin dns. If I use that instead of cp[0] in terraform the config gets applied to a random control plane node.Environment
0.1.0-alpha.9
The text was updated successfully, but these errors were encountered: