Skip to content

docs: add talosconfig file#359

Merged
rothgar merged 1 commit intosiderolabs:mainfrom
Iheanacho-ai:talosconfig-file
Feb 13, 2026
Merged

docs: add talosconfig file#359
rothgar merged 1 commit intosiderolabs:mainfrom
Iheanacho-ai:talosconfig-file

Conversation

@Iheanacho-ai
Copy link
Member

fixes #300

@talos-bot talos-bot moved this to In Review in Planning Feb 10, 2026
@Iheanacho-ai Iheanacho-ai requested a review from smira February 10, 2026 16:48
@rothgar
Copy link
Member

rothgar commented Feb 10, 2026

You should also have an example of what the config looks like with Omni since Omni becomes your endpoint and manages certs.

Copy link
Member

@smira smira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would split the whole document into two sections: talosconfig for bare Talos and talosconfig when going via Omni. Most of the fields are exclusively used only in one of the modes, and some fields have totally different meaning.

Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
@rothgar
Copy link
Member

rothgar commented Feb 13, 2026

/m

@rothgar rothgar merged commit 22d893c into siderolabs:main Feb 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document talosconfig fields

5 participants