-
Notifications
You must be signed in to change notification settings - Fork 46
docs: add documentation about ssa behaviour in talos v1.13 #280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
* clean up inline/extra manifests documentation * add documentation about the pruning process Signed-off-by: Orzelius <33936483+Orzelius@users.noreply.github.com>
f9495e6 to
5b357e2
Compare
| > Note: Pruning is supported from Talos and talosctl v1.13 onwards. | ||
| Pruning of resources from the cluster occurs when any services were deleted or disabled. | ||
| For example if [kube-proxy](../../talos/v1.12/reference/configuration/v1alpha1/config.mdx#proxy) was disabled in the machine configuration the resources associated with it would be deleted at this stage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a way to create a link that automatically takes to the latest reference version here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, you'd have to use the latest variable
| Updated bootstrap manifests might come with a new Talos version (e.g. CoreDNS version update), or might be the result of machine configuration change. | ||
|
|
||
| > Note: The `upgrade-k8s` command never deletes any resources from the cluster: they should be deleted manually. | ||
| 6. Unneeded resources are pruned from the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would put a note here that this applies to Talos 1.13+
|
|
||
| If you need to reapply or update these manifests after the cluster has been created, use the [Kubernetes upgrade](./upgrading-kubernetes) process. | ||
| Specify the same Kubernetes version that’s currently running in your cluster to ensure that only the manifests are reapplied, without performing a version upgrade. | ||
| If you need to prune unwanted resources or update the resources, use the [Kubernetes upgrade](./upgrading-kubernetes) process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and probably here, starting with Talos 1.13+
related to siderolabs/talos#12560, siderolabs/talos#12362