docs: support ca rotation with Omni#354
Draft
oguzkilcan wants to merge 1 commit intosiderolabs:mainfrom
Draft
Conversation
Member
Author
|
This needs to be merged after Omni 1.6 is released. |
utkuozdemir
reviewed
Feb 9, 2026
|
|
||
| `omnictl` needs to be able to reach your Omni instance, Image Factory (Omni uses the default [Image Factory](https://factory.talos.dev/) if not configured otherwise) and Talos nodes over the network. | ||
|
|
||
| Also, your Omni instance needs to be able to reach the Talos nodes over the network. If your nodes are behind a firewall, in a private network, or otherwise not directly reachable, you would need to configure a load balancer to forward TCP port 50000 to reach the nodes for Talos API access. |
Member
Author
There was a problem hiding this comment.
Omni instance doesn't need to reach Talos nodes directly. It reaches them over SideroLink. Talos nodes need to be able to initiate the connection though.
Iheanacho-ai
reviewed
Feb 9, 2026
| Run the following command to rotate the Talos API CA: | ||
|
|
||
| ```shell | ||
| $ omnictl cluster -n <cluster-name> secret rotate talos-ca |
| Talos sets up root certificate authorities with the lifetime of 10 years, and all Talos and Kubernetes API certificates are issued by these root CAs. | ||
| So the rotation of the root CA is only needed if: | ||
|
|
||
| - you want to revoke access to the cluster for a leaked break-glass `kubeconfig` or `talosconfig`; |
Member
There was a problem hiding this comment.
Start each list with Capital letters
|
|
||
| There are some details which make Talos and Kubernetes API root CA rotation a bit different, but the general flow is the same: | ||
|
|
||
| - generate new CA certificate and key; |
Member
There was a problem hiding this comment.
Start each list with capital letters
| At the end of the flow, old CA is completely removed from the cluster, so all certificates issued by it will be considered invalid. | ||
|
|
||
| Omni internally handles all these steps in three stages: | ||
| - PRE-ROTATE: Add a new CA certificate as 'accepted', |
Member
There was a problem hiding this comment.
embolden this PRE-ROTATE, same goes with ROTATE and POST-ROTATE
| Run the following command to rotate the Kubernetes API CA: | ||
|
|
||
| ```shell | ||
| $ omnictl cluster -n <cluster-name> secret rotate kubernetes-ca |
Member
There was a problem hiding this comment.
remove the shell command here
Add documentation for CA rotation for Kubernetes and Talos with `omnictl` Signed-off-by: Oguz Kilcan <oguz.kilcan@siderolabs.com>
oguzkilcan
force-pushed
the
docs/ca-rotation
branch
from
f2ba5fc to
6043fc0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add documentation for CA rotation for Kubernetes and Talos with
omnictl