Modifying network configuration, adding ipv6 address

[idc77]

I have rented 4 VMs and am trying Talos in a live environment.
There is 1c 3w.
The instances have ipv4 and ipv6 addresses.
When I set them up, DHCP wasn't working and I had to VNC to manually set ipv4 addresses and gateways and dns.

I have applied the new machine config by editing the controlplane.yaml and worker.yaml files and applying them.
The documentation could be better in that regard.

Now I wanted to add the IPv6 addresses to the instances.
However my controlplane.yaml and worker.yaml both have

network: {}

when I

talosctl get meta -n cp0.remote --talosconfig talosconfig

it returns a yaml type response.

NODE            NAMESPACE   TYPE      ID     VERSION   VALUE
cp0.remote   runtime     MetaKey   0x0a   1         addresses:
    - address: 2.3.4.5/22
      linkName: enp7s0
      family: inet4
      scope: global
      flags: permanent
      layer: platform
links:
    - name: enp7s0
      logical: false
      up: true
      mtu: 0
      kind: ""
      type: ether
      layer: platform
routes:
    - family: inet4
      dst: ""
      src: ""
      gateway: 1.2.3.4
      outLinkName: enp7s0
      table: main
      scope: global
      type: unicast
      flags: ""
      protocol: static
      layer: platform
hostnames:
    - hostname: cp0.remote
      domainname: ""
      layer: platform
resolvers:
    - dnsServers:
        - 8.8.8.8
      layer: platform
timeServers:
    - timeServers:
        - time.cloudflare.com
      layer: platform
operators: []
externalIPs: []

talosctl edit machineconfig is the same file as controlplane.yaml or worker.yaml

So...
How do I

• get the current config
• modify the current config
• apply the modified config
  ?

[smira]

So I guess you used the console dashboard to configure the network manually, that's what you see in talosctl get meta.

You can leave that as it is, or convert it to machine config (up to you).

Talos machine configuration is a YAML document which you can modify by editing it (it gets downloaded to your editor, and re-applied back with your edits), you can patch it.

I would pick rather patch it, as it's the easiest way (also, if you're considering production, see these notes, or you can use Omni which automates config management for you).

So if you look at the config reference, you can come up with a patch like:

machine:
  network:
   interfaces:
    - interface: enp7s0
       addresses: 
         - 2010:b7b::1/64 # your IPv6 address goes here

And patch the machine config with (the easiest way): talosctl -n <machine IP> patch mc -p @ipv6.patch

For IPv6 you would probably also need to set up routes, but you can simply adjust the patch to include routes as well.

[idc77]

Thank you Andrey :)
Great answer, really appreciate it

[idc77]

decode error: yaml: line 5: mapping values are not allowed in this context

[idc77]

Indentation was off

machine:
  network:
    interfaces:
      - interface: enp7s0
        addresses:
          - 2010:b7b::1/64 # your IPv6 address goes here