Remove direct zap dependecy in operator and kube-agent-updater #50960
+88
−29
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.
This PR removes the direct zap dependency from the operator and kube-agent-updater.
This is a breaking change and must not be backported as the
-zap-*
CLI flags are removed. Those flags were not documented nor used directly, but users might have set them via theextraArgs
chart value.I switched logs by default to JSON and did not add a --log-format flag. I add such flag if you think this is necessary.
Changelog: Remove the
zap-log-level
,zap-devel
,zap-encoder
andzap-stacktrace-level
flags in the operator. Use--log-level
instead.Changelog: Remove the
zap-log-level
,zap-devel
,zap-encoder
andzap-stacktrace-level
flags in the teleport-kube-agent-updater. Use--log-level
instead.Changelog: The operator now logs using JSON by default.
Changelog: The kube-agent-updater now logs using JSON by default.