You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bootstrap failing with failed to verify certificate: x509 #61
Hey, Talm is storing talosconfig in the same directroy with the project, you can copy your talosconfig into root project directory, or override path in Chartt.yaml
> ./talm init
Created secrets.yaml
generating PKI and tokens
Created talosconfig
Created values.yaml
Created charts/talm/Chart.yaml
Created charts/talm/templates/_helpers.tpl
Created Chart.yaml
Created templates/_helpers.tpl
Created templates/controlplane.yaml
Created templates/worker.yaml
machine:
network:
interfaces:
- deviceSelector:
physical: true # should select any hardware network device, if you have just one, it will be selecteddhcp: truevip:
ip: 192.168.121.100
Great you solved it, could you describe what was the misalignment between the two generated template? If I remember well, some options help to debug such as talm option --full to see all fields in template output
Per @veith4f's confirmation above (2026-04-06), the bootstrap failure was a misalignment between the default values.yaml generated by talm init and the node's actual network — not a bug in talm itself. Following the install guide and editing values.yaml to match the cluster network resolves it; --with-secrets on apply was also relevant.
Closing as resolved. If anyone still hits an x509 failure after aligning values.yaml to their network, please open a fresh issue with the rendered config and talosctl output.
Activity
kvaps commentedon May 29, 2025
Hey, Talm is storing
talosconfigin the same directroy with the project, you can copy your talosconfig into root project directory, or override path inChartt.yamlNikola-Milovic commentedon May 29, 2025
Andrei Kvapil (@kvaps) I believe that is the case
I'll redo it again
vagrant up(after wgeting 1.10 talos image)Is there a way to apply a patch while generating the configs? Maybe that is causing issues
Controlplane
nodes/cp1.yamlAnd my patch is
lb0o commentedon Jul 23, 2025
Hi, I think you need to properly edit the values.yaml that is generated after talm init
It looks like a templating issue with default network (from default values.yaml) that does not align with your nodes ip
shepses commentedon Apr 5, 2026
Same issue here. lb0o What does "default network" mean?
I can bootstrap a cluster with talosctl but the instructions for talm as laid out in https://cozystack.io/docs/v1/install/kubernetes/talm/
don't work for me.
Andrei Kvapil (@kvaps) any ideas?
I am on MacOs Ventura.
here is my values.yaml
here is my full node1.yaml
talosconfig
shepses commentedon Apr 5, 2026
Fixed! Andrei Kvapil (@kvaps) lb0o Nikola Milovic (@Nikola-Milovic).
Guide under https://cozystack.io/docs/v1/install/kubernetes/talm/ says:
What worked:
kvapil I think
talmshould automatically look for and use the secrets.yaml if it exists.lb0o commentedon Apr 6, 2026
Great you solved it, could you describe what was the misalignment between the two generated template? If I remember well, some options help to debug such as talm option --full to see all fields in template output
shepses commentedon Apr 6, 2026
did you try to apply with --with-secrets parameter?
lexfrei commentedon Apr 16, 2026
Per @veith4f's confirmation above (2026-04-06), the bootstrap failure was a misalignment between the default
values.yamlgenerated bytalm initand the node's actual network — not a bug in talm itself. Following the install guide and editingvalues.yamlto match the cluster network resolves it;--with-secretson apply was also relevant.Closing as resolved. If anyone still hits an x509 failure after aligning
values.yamlto their network, please open a fresh issue with the rendered config andtalosctloutput.