Skip to content
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

Operator should restart only affected components on changing config overrides #45

Open
koct9i opened this issue Nov 8, 2023 · 1 comment
Assignees
Labels
backlog Backlog

Comments

@koct9i
Copy link
Collaborator

koct9i commented Nov 8, 2023

Subj. Looks line now it does full-cluster restart.

@savnadya savnadya added the backlog Backlog label Mar 20, 2024
@l0kix2 l0kix2 self-assigned this Jun 25, 2024
@l0kix2
Copy link
Collaborator

l0kix2 commented Jul 23, 2024

In #314 i've added a test that configOverrides change is detected by the operator. Apart from the main check I've added check, that only a component which is mentioned in configOverrides is recreated, but master for example is not. I couldn't reproduce the full update.
If someone can reproduce (or better change the test so it would fail) on the latest version of the operator, let me know. Otherwise maybe we should consider it outdated and close.

//cc @koct9i @sgburtsev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Backlog
Projects
Status: No status
Development

No branches or pull requests

3 participants