Skip to content

chore: switch BootstrapSynchronisation feature gate to opt-out #3590

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.

Sign up for GitHub

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

Open
rzetelskik wants to merge 3 commits into
base: master
Choose a base branch
from
+10 −5
Open

chore: switch BootstrapSynchronisation feature gate to opt-out #3590

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
de49880
chore: switch BootstrapSynchronisation feature gate to opt-out
rzetelskik Aug 13, 2026
84498e8
docs: adjust docs to BootstrapSynchronisation opt-out
rzetelskik Aug 13, 2026
7237420
docs: add BootstrapSynchronisation feature gate switch to opt-out cha…
rzetelskik Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,10 @@
Previously every node expected to exist in the Kubernetes state was required to be reported and UP, including nodes
that hadn't joined yet and couldn't report their status.
[#3530](https://github.com/scylladb/scylla-operator/pull/3530)
- The `BootstrapSynchronisation` feature gate is now enabled by default, making the bootstrap barrier opt-out. It
remains a no-op below ScyllaDB 2025.2.0, where the operator does not inject the `scylladb-bootstrap-barrier` init
container regardless of the gate.
[#3590](https://github.com/scylladb/scylla-operator/pull/3590)
- Restored the multi-datacenter documentation, which was dropped by the docs restructuring in 1.21. The guide for
deploying a multi-datacenter ScyllaDB cluster, and the guides for preparing interconnected EKS and GKE clusters to
run it on, are available again under Deploy ScyllaDB and Provision infrastructure respectively.
Expand Down
4 changes: 2 additions & 2 deletions docs/source/reference/feature-gates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,8 @@ additionalArgs:
- `true`
- v1.11
* - `BootstrapSynchronisation`
- `false`
- v1.19
- `true`
- v1.22
:::

- **Default** — whether the feature is enabled when you don't set it explicitly.
Expand Down
2 changes: 1 addition & 1 deletion docs/source/understand/bootstrap-sync.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ If any node is missing a host ID, has not yet reported, does not list another no
* - Requirement
- Value
* - Feature gate
- `BootstrapSynchronisation` (default off since v1.19)
- `BootstrapSynchronisation` (default on since v1.22)
* - Minimum ScyllaDB version
- 2025.2
```
Expand Down
5 changes: 3 additions & 2 deletions pkg/features/features.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ const (

// BootstrapSynchronisation enables a barrier which ensures bootstrap preconditions are met before starting a ScyllaDB node attempting to join the cluster.
// alpha: v1.19
// beta: v1.22
BootstrapSynchronisation featuregate.Feature = "BootstrapSynchronisation"
)

Expand All @@ -36,8 +37,8 @@ func init() {
PreRelease: featuregate.Beta,
},
BootstrapSynchronisation: {
Default: false,
PreRelease: featuregate.Alpha,
Default: true,
PreRelease: featuregate.Beta,
},
}))
}
Loading