budimanjojo/talhelper

System extensions example

runningman84 opened this issue · 7 comments

runningman84 commented

It would be great to have some example how to enable system extensions like iscsi. I tried the extensions parameter in the node object but got a deprecation warning in talosctl.

What is the correct way to that?

runningman84 commented

I tried that example once but did not see any change in the generated machine configs but I will try to reproduce that...

budimanjojo commented

The change should only be in the machine.install.image which is the installer url with the schematic ID where that extension should be included.

runningman84 commented

okay my config looks like this

clusterName: k8s-dev
talosVersion: v1.6.6
endpoint: https://10.0.30.80:6443
additionalApiServerCertSans:
- home-cluster-dev.local
- k8s-dev.home.foo.bar
#- 10.0.30.80
#  - 10.0.30.81
#  - 10.0.30.82
#  - 10.0.30.83
additionalMachineCertSans:
  - 10.0.30.81
  - 10.0.30.82
  - 10.0.30.83
allowSchedulingOnMasters: true
nodes:
  - hostname: master1
    ipAddress: 10.0.30.81
    installDisk: /dev/sda
    controlPlane: true
    disableSearchDomain: true
    nameservers:
      - 1.1.1.1
      - 8.8.8.8
      - 8.8.4.4
    networkInterfaces:
      - interface: enp0s3
      #   addresses:
      #     - 10.0.30.81/24
      #   routes:
      #     - network: 0.0.0.0/0
      #       gateway: 10.0.30.1
      #   mtu: 1500
        dhcp: true
        vip:
          ip: 10.0.30.80
    schematic:
      customization:
        systemExtensions:
          officialExtensions:
            - siderolabs/intel-ucode
            - siderolabs/iscsi-tools
            - siderolabs/util-linux-tools
            - siderolabs/gasket-driver
...

but the result is just this

  install:
    disk: /dev/sda
    image: ghcr.io/siderolabs/installer:v1.6.6
    wipe: false

it does not look like the extensions are included?

runningman84 commented

sorry I used some old version of talhelper... the new one works!

  • ❤️1
runningman84 commented

@budimanjojo with reset and re apply the extensions were active. Unfortunately after a node shutdown and start the extensions were lost again. Do you have any idea how that can happen?

budimanjojo commented

That's weird and I don't think it has anything to do with talhelper but rather the OS side problem. Maybe the log of the kernel might show you something.