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

Make loglevel configurable in ScyllaOperatorConfig #2314

Open
rzetelskik opened this issue Jan 10, 2025 · 0 comments
Open

Make loglevel configurable in ScyllaOperatorConfig #2314

rzetelskik opened this issue Jan 10, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@rzetelskik
Copy link
Member

What should the feature do?

Loglevel of particular components should be configurable through ScyllaOperatorConfig.

What is the use case behind this feature?

Allows for finer granularity and is a step towards having a centralised config.

Anything else we need to know?

For backwards compatibility, the flag provided to the binary should take precedence.

Duplicate of #836.

/lifecycle frozen
/priority important-soon

@rzetelskik rzetelskik added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 10, 2025
@scylla-operator-bot scylla-operator-bot bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant