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

Deprecation warning event spamming and incomplete association with operand #785

Closed
jaideepr97 opened this issue Sep 27, 2022 · 0 comments · Fixed by #786
Closed

Deprecation warning event spamming and incomplete association with operand #785

jaideepr97 opened this issue Sep 27, 2022 · 0 comments · Fixed by #786

Comments

@jaideepr97
Copy link
Collaborator

jaideepr97 commented Sep 27, 2022

Describe the bug
Currently the operator spams deprecation warning events on the cluster when any of the soon-to-be-deprecated SSO/dex related fields/env vars are used. There are too many events being generated and they aren't timestamped or properly associated with the affected CR

To Reproduce
Steps to reproduce the behavior:

Install/run the operator and have a CR using the old SSO config method or specifying the DISABLE_DEX env var in the subscription

Expected behavior
A single event is generated with proper timestamps and CR association, and its count updated if multiple occurances of the event are observed, instead of spamming events and polluting the cluster

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
https://issues.redhat.com/browse/GITOPS-2230

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant