Talos and Kube

fd0 stores Talos contexts and Kubernetes configs as typed secrets. It renders deterministic config files and can merge them into your normal tool config after sync.

Talos

$ fd0 talos add --from-config ~/.talos/config \
    --import-context prod --scope work
$ fd0 talos enable --merge
$ fd0 sync

$ talosctl --talosconfig ~/.talos/config.fd0 config contexts

Enabled Talos refresh means every fd0 sync re-renders ~/.talos/config.fd0. With --merge, fd0 also folds those contexts into ~/.talos/config.

Kubernetes

$ fd0 kube add prod --from-config ~/.kube/config \
    --import-context admin@prod --scope work
$ fd0 kube enable --merge
$ fd0 sync

$ kubectl --kubeconfig ~/.kube/config.fd0 get nodes

Enabled Kube refresh means every fd0 sync re-renders ~/.kube/config.fd0. With --merge, fd0 also folds those entries into ~/.kube/config.

Current context

When fd0 renders exactly one Talos or Kube context, it marks that context current. When it merges into an existing user config, it preserves your existing current context unless you change it yourself.

Day-0 Talos credentials

fd0 talos new can generate cluster PKI and store the disaster-recovery secrets.yaml bundle. That path shells out to talosctl. Normal add/list/render/merge paths are pure Go.