omni/client/api
Artem Chernyshev 5047a625f7
Some checks failed
default / default (push) Has been cancelled
default / e2e-backups (push) Has been cancelled
default / e2e-cluster-import (push) Has been cancelled
default / e2e-forced-removal (push) Has been cancelled
default / e2e-omni-upgrade (push) Has been cancelled
default / e2e-scaling (push) Has been cancelled
default / e2e-short (push) Has been cancelled
default / e2e-short-secureboot (push) Has been cancelled
default / e2e-templates (push) Has been cancelled
default / e2e-upgrades (push) Has been cancelled
default / e2e-workload-proxy (push) Has been cancelled
feat: compute unique token status for each node
The node token status can be used to check if the machine has the unique
token generated. It also shows the exact token state:

- `NONE` - token is supported, but not yet generated.
- `UNSUPPORTED` - Talos is < 1.6.x, so token won't be generated.
- `EPHEMERAL` - token is generated, but is not persistent, so join token
  rotation and machine reboot will make the node to disconnect.
- `PERSISTENT` - token is generated and is persisted to the `META`
  partition.

If the node unique status is `NONE` the same controller will try to
generate node unique token.

Fixes: https://github.com/siderolabs/omni/issues/1348

Signed-off-by: Artem Chernyshev <artem.chernyshev@talos-systems.com>
2025-07-30 11:57:24 +03:00
..
common test: improve workload proxying tests 2025-06-04 17:41:30 +02:00
google/rpc fix: properly support the PXE and ISO machines in the secure tokens flow 2025-03-03 19:54:58 +03:00
omni feat: compute unique token status for each node 2025-07-30 11:57:24 +03:00
talos/machine chore: rekres, bump deps, Go, Talos and k8s versions, satisfy linters 2025-07-11 18:23:48 +02:00
v1alpha1 chore: initial commit 2024-02-29 17:19:57 +04:00