Repository navigation
Document the operator's logging flags - #1074
Open
Manishram-ai wants to merge 1 commit into
Open
Manishram-ai wants to merge 1 commit into
Manishram-ai wants to merge 1 commit into
Conversation
This was referenced Nov 1, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #173
You can change how the operator logs with controller-runtime's zap flags, but they aren't documented anywhere right now. The only way to find them is
--helpor readingmain.go. This adds a short section about them to the user guide, right after the one about Flink cluster logs.It covers what each flag does and how to change them on a running operator. It also explains why
make rungives you console logs at debug level, while the release YAML and the Helm chart give you JSON at info level. The Helm chart doesn't have a value for extra args yet, so for now the docs tell people to edit the Deployment. If that sounds useful, I can send a small follow-up that adds one to the chart.I ran the operator locally with these flags to make sure the docs are right. The only surprise was the timestamp format. The
--helptext says it defaults toepoch, but the logs actually use RFC3339, so that's what I wrote in the docs.