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

K8po/monit 43152 templatize pixie namespace #565

Merged
merged 8 commits into from
May 14, 2024

Conversation

akodali18
Copy link
Contributor

When the operator is deployed on a custom namespace, the controller manager tries to delete secrets that pertain to pixie from the default namespace irrespective of whether pixie experimental features are ON/OFF, thus producing noisy logs that consume cost/resources and noisy alerts for the customer.

wf-jenkins and others added 6 commits May 1, 2024 21:47
…se causes errors as controller manager when deployed in a custom namespace tries to delete all resources atm.We currently do allow deploying k8s operator in a custom namespace which gives redundant logs for pixie eventhough it is experimental and turned OFF by default. This is the reason we went with this solution instead of modifying controller manager code to delete only enabled resources.
@akodali18 akodali18 merged commit 71e741c into main May 14, 2024
4 of 5 checks passed
@akodali18 akodali18 deleted the k8po/MONIT-43152-templatize-pixie-namespace branch May 14, 2024 04:18
akodali18 added a commit that referenced this pull request May 24, 2024
* Fix generate_yamls to templatize namespace for Pixie CR. This otherwise produces noisy error logs in controller manager when deployed in a custom namespace as it tries to delete all the components.

--------

(cherry picked from commit 71e741c)
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 this pull request may close these issues.

3 participants