Skip to content

Additional debug logs from DependentPredicate #5764

@cliles

Description

@cliles

Feature Request

Describe the problem you need a feature to resolve.

When using an ansible-operator I have an issue when my operator starts looping reconciliation due to dependent resource updates. It is difficult to quickly pinpoint the cause. The current debug logging level helps by providing the information as to what dependent resource triggered the update, but there is no verbosity that can be enabled to show the why or delta on that resource from the predicate function.

Describe the solution you'd like.

It would be helpful to have the diff between old and new objects printed in debug log level. Maybe some extra verbosity is appropriate, and bonus points to be able to enable/disable it via a CR annotation.

https://github.com/operator-framework/operator-lib/blob/main/predicate/dependent.go#L86

Metadata

Metadata

Labels

language/ansibleIssue is related to an Ansible operator projectlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions