Skip to content

Commit 2474328

Browse files
committed
Formatting
1 parent 54fb3b5 commit 2474328

File tree

2 files changed

+30
-26
lines changed

2 files changed

+30
-26
lines changed

README.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -600,32 +600,6 @@ talos_backup_schedule = "0 * * * *"
600600
To recover from a snapshot, please refer to the Talos Disaster Recovery section in the [Documentation](https://www.talos.dev/latest/advanced/disaster-recovery/#recovery).
601601
</details>
602602

603-
<!-- Talos Discovery Service -->
604-
<details>
605-
<summary><b>Talos Discovery Service</b></summary>
606-
607-
Talos supports two node discovery mechanisms:
608-
609-
- **Discovery Service Registry** (default): A public, external registry operated by Sidero Labs that works even when Kubernetes is unavailable. Nodes must have outbound access to TCP port 443 to communicate with it.
610-
- **Kubernetes Registry**: Relies on Kubernetes Node metadata stored in etcd.
611-
612-
This module uses the discovery service to perform additional health checks during Talos upgrades, Kubernetes upgrades, and Kubernetes manifest synchronization. If no discovery mechanism is enabled, these additional checks will be skipped.
613-
614-
> :warning: **Important:** Kubernetes-based discovery is **incompatible by default** with Kubernetes **v1.32+** due to the `AuthorizeNodeWithSelectors` feature gate, which restricts access to Node metadata. This can cause broken discovery behavior, such as failing or incomplete results from `talosctl health` or `talosctl get members`.
615-
616-
##### Example Configuration
617-
618-
```hcl
619-
# Disable Kubernetes-based discovery (deprecated in Kubernetes >= 1.32)
620-
talos_kubernetes_discovery_service_enabled = false
621-
622-
# Enable the external Sidero Labs discovery service (default)
623-
talos_siderolabs_discovery_service_enabled = true
624-
```
625-
626-
For more details, refer to the [official Talos discovery guide](https://www.talos.dev/latest/talos-guides/discovery/).
627-
</details>
628-
629603
<!-- Talos Bootstrap Manifests -->
630604
<details>
631605
<summary><b>Talos Bootstrap Manifests</b></summary>
@@ -708,6 +682,32 @@ talos_extra_inline_manifests = [
708682

709683
</details>
710684

685+
<!-- Talos Discovery Service -->
686+
<details>
687+
<summary><b>Talos Discovery Service</b></summary>
688+
689+
Talos supports two node discovery mechanisms:
690+
691+
- **Discovery Service Registry** (default): A public, external registry operated by Sidero Labs that works even when Kubernetes is unavailable. Nodes must have outbound access to TCP port 443 to communicate with it.
692+
- **Kubernetes Registry**: Relies on Kubernetes Node metadata stored in etcd.
693+
694+
This module uses the discovery service to perform additional health checks during Talos upgrades, Kubernetes upgrades, and Kubernetes manifest synchronization. If no discovery mechanism is enabled, these additional checks will be skipped.
695+
696+
> :warning: **Important:** Kubernetes-based discovery is **incompatible by default** with Kubernetes **v1.32+** due to the `AuthorizeNodeWithSelectors` feature gate, which restricts access to Node metadata. This can cause broken discovery behavior, such as failing or incomplete results from `talosctl health` or `talosctl get members`.
697+
698+
##### Example Configuration
699+
700+
```hcl
701+
# Disable Kubernetes-based discovery (deprecated in Kubernetes >= 1.32)
702+
talos_kubernetes_discovery_service_enabled = false
703+
704+
# Enable the external Sidero Labs discovery service (default)
705+
talos_siderolabs_discovery_service_enabled = true
706+
```
707+
708+
For more details, refer to the [official Talos discovery guide](https://www.talos.dev/latest/talos-guides/discovery/).
709+
</details>
710+
711711
<!-- Lifecycle -->
712712
## :recycle: Lifecycle
713713
The [Talos Terraform Provider](https://registry.terraform.io/providers/siderolabs/talos) does not support declarative upgrades of Talos or Kubernetes versions. This module compensates for these limitations using `talosctl` to implement the required functionalities. Any minor or major upgrades to Talos and Kubernetes will result in a major version change of this module. Please be aware that downgrades are typically neither supported nor tested.

variables.tf

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -822,6 +822,7 @@ variable "talos_ccm_enabled" {
822822
default = true
823823
description = "Enables the Talos Cloud Controller Manager (CCM) deployment."
824824
}
825+
825826
variable "talos_ccm_version" {
826827
type = string
827828
default = "v1.9.1" # https://github.com/siderolabs/talos-cloud-controller-manager
@@ -875,6 +876,7 @@ variable "hcloud_ccm_enabled" {
875876
default = true
876877
description = "Enables the Hetzner Cloud Controller Manager (CCM)."
877878
}
879+
878880
variable "hcloud_ccm_helm_repository" {
879881
type = string
880882
default = "https://charts.hetzner.cloud"
@@ -970,6 +972,7 @@ variable "cilium_enabled" {
970972
default = true
971973
description = "Enables the Cilium CNI deployment."
972974
}
975+
973976
variable "cilium_helm_repository" {
974977
type = string
975978
default = "https://helm.cilium.io"
@@ -1394,6 +1397,7 @@ variable "prometheus_operator_crds_enabled" {
13941397
default = true
13951398
description = "Enables the Prometheus Operator Custom Resource Definitions (CRDs) deployment."
13961399
}
1400+
13971401
variable "prometheus_operator_crds_version" {
13981402
type = string
13991403
default = "v0.82.1" # https://github.com/prometheus-operator/prometheus-operator

0 commit comments

Comments
 (0)