Open grzesuav opened 4 months ago
Initial idea would be to add logr.Logger
interface, configure some initial logger (like zap) and add a flag to enable verbose logging - of course as writing to sdtout it would conflict with output:stdout
but it is expected
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Recently I stumble upon a situation when running controller gen had no effect
for the
crd
gen, but worked fine forobject
gen(it produced output)
When I wanted to dig into it, I realized there is no way to enable
verbose
output in controller-gen, which would help to debug it.Would be nice to have this feature