Andrey Smirnov 263f699ea4
chore: annotate extensions with tiers
Fixes #10940

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
2025-08-26 20:58:30 +04:00
..
2025-05-29 11:32:59 +05:30
2025-08-26 20:58:30 +04:00
2025-02-19 15:12:47 +05:30

Nebula

https://github.com/slackhq/nebula

Installation

See Installing Extensions.

Usage

Configure the extension via ExtensionServiceConfig document. You can add any nebula related configuration and these will be executed at Nebula startup.

---
apiVersion: v1alpha1
kind: ExtensionServiceConfig
name: nebula
configFiles:
  - content: |
        pki:
          ca: /usr/local/etc/nebula/ca.crt
          cert: /usr/local/etc/nebula/node.crt
          key: /usr/local//etc/nebula/node.key
    mountPath: /usr/local/etc/nebula/config.yml
  - content: |
        -----BEGIN NEBULA CERTIFICATE-----
        -----END NEBULA CERTIFICATE-----
    mountPath: /usr/local/etc/nebula/ca.crt
  - content: |
        -----BEGIN NEBULA CERTIFICATE-----
        -----END NEBULA CERTIFICATE-----
    mountPath: /usr/local/etc/nebula/node.crt
  - content: |
        -----BEGIN NEBULA ED25519 PRIVATE KEY-----
        -----END NEBULA ED25519 PRIVATE KEY-----
    mountPath: /usr/local/etc/nebula/node.key

Then apply the patch to your node's MachineConfigs

talosctl patch mc -p @nebula-config.yaml

You will then be able to verify that it is in place with the following command

talosctl get extensionserviceconfigs

NODE          NAMESPACE   TYPE                     ID           VERSION
mynode   runtime     ExtensionServiceConfig   nebula            1