Replies: 1 comment
-
If using
This depends on Oracle Cloud, not Talos. Usually in the clouds public IPs are not assigned to the machine, but rather mapped 1:1 on the infrastructure side. The way you assigned public IP is correct for Talos Linux, but not sure how it should work with Oracle Linux. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey peoples,
I am stuck on expanding a multi-cloud deployment with some worker nodes in the Oracle Cloud. My controlplane is running in Hetzner and I have some Proxmox VMs, Strato VServers and AWS EC2s as workers, all work great. Now I want to add some Oracle VMs. If I run
talosctl get --insecure nodeaddresses --nodes 123.123.123.123
(123.123.123.123
is a Oracle VM booted up with TalosOS) I getbecause the networking on Oracle, the VM does not know it public IP. I can assign the public IP to the certSANs
to make the certificate working, but once I apply the machine config
talosctl apply-config --nodes 123.123.123.123 --file worker-123.123.123.123.yaml --insecure
the API is not reachable anymore because Talos is not configured to listen on the public IP123.123.123.123
and it does not know about it from thenodeaddresses
.talosctl edit machineconfig --nodes 123.123.123.123 # rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 123.123.123.123:50000: i/o timeout"
How can I provider this public IP in the machine configuration? I tried different variations of (only the custom part of the config)
Beta Was this translation helpful? Give feedback.
All reactions