Skip to content

Commit 819ca62

Browse files
committed
Update links in README.md
1 parent 2474328 commit 819ca62

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -606,7 +606,7 @@ To recover from a snapshot, please refer to the Talos Disaster Recovery section
606606

607607
### Toggle Component Deployment in Bootstrap Manifests
608608

609-
During the cluster provisioning phase, each component manifest is applied using Talos's bootstrap manifests feature. However, this also means that the manifests are **re-applied** every time `terraform apply` is run, as part of the [automated Kubernetes upgrade process](https://www.talos.dev/v1.8/kubernetes-guides/upgrading-kubernetes/#automated-kubernetes-upgrade) triggered by the module.
609+
During the cluster provisioning phase, each component manifest is applied using Talos's bootstrap manifests feature. However, this also means that the manifests are **re-applied** every time `terraform apply` is run, as part of the [automated Kubernetes upgrade process](https://www.talos.dev/latest/kubernetes-guides/upgrading-kubernetes/#automated-kubernetes-upgrade) triggered by the module.
610610

611611
This behavior can cause issues if you want to use GitOps tools like **FluxCD** or **ArgoCD** to manage the lifecycle of these components. Since Talos manages the application lifecycle, any changes made by FluxCD or ArgoCD (e.g., annotations or labels) may be overwritten or removed during upgrades, leading to conflicts.
612612

@@ -649,7 +649,7 @@ cluster_autoscaler_nodepools = [
649649
]
650650
```
651651

652-
> **Note:** Disabling a component **does not delete** its deployed resources. This is explicitly stated in the [Talos documentation](https://www.talos.dev/v1.8/kubernetes-guides/upgrading-kubernetes/#automated-kubernetes-upgrade).
652+
> **Note:** Disabling a component **does not delete** its deployed resources. This is explicitly stated in the [Talos documentation](https://www.talos.dev/latest/kubernetes-guides/upgrading-kubernetes/#automated-kubernetes-upgrade).
653653

654654
After removing the component from the bootstrap manifests, you can either delete the existing resources manually before reapplying, or allow FluxCD/ArgoCD to take over their reconciliation and ongoing management.
655655

0 commit comments

Comments
 (0)