-
Notifications
You must be signed in to change notification settings - Fork 108
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
[deckhouse] enable ha only if clusterIsBootstrapped #8275
Conversation
Signed-off-by: Mikhail Scherba <mikhail.scherba@flant.com>
🔴 E2e for yandex-cloud WithoutNAT;containerd;1.25 was failed. Use:
Workflow details (1 job failed)Yandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: 🔴 |
/e2e/abort yandex-cloud;WithoutNAT;containerd;1.25 8847401930 8847401930-1-con-1-25 /sys/deckhouse-oss/install:pr8275 redos@178.154.201.200 |
🟢 Workflow details🟢 |
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: 🟢 |
Signed-off-by: Mikhail Scherba <mikhail.scherba@flant.com>
Cherry pick PR 8311 to the branch release-1.59 successful! |
Signed-off-by: Mikhail Scherba <mikhail.scherba@flant.com>
Description
This PR introduces an additional condition for the
deckhouse
module high availability mode:.Values.global.clusterIsBootstrapped
values has to be true.Why do we need it, and what problem does it solve?
This measure should prevent deckhouse operator from switching to high availability mode when the cluster hasn't got bootstrapped yet, minimizing the impact on the whole bootstrapping process.
Why do we need it in the patch release (if we do)?
It may come in handy as soon as possible.
What is the expected result?
If a cluster hasn't bootstrapped yet,
deckhouse
operator shouldn't be run in high availability mode.Checklist
Changelog entries