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

Ignore read Logs by phase kubernetes operator in Phase App #16

Open
dodistyo opened this issue Sep 16, 2024 · 1 comment
Open

Ignore read Logs by phase kubernetes operator in Phase App #16

dodistyo opened this issue Sep 16, 2024 · 1 comment
Assignees

Comments

@dodistyo
Copy link
Contributor

dodistyo commented Sep 16, 2024

Is it possible to ignore the logs that comes from the phase kubernetes operator?
because logging every read event from the operator is kinda pointless and it will generate too many logs which is I think it's unnecessary.
Also i want to address another issue related with operator polling, I don't think that the field pollingInterval is working when set. looking at the code and it looks like it's being hard coded to 60s if i'm not mistaken. With the current implementation, I don't know if we can make it works or not. @nimish-ks

@nimish-ks nimish-ks self-assigned this Sep 16, 2024
@nimish-ks
Copy link
Member

  1. Will add a variable in values.yaml that will control logging verbosity that a user can control in the next release
  2. The polling interval is currently hard-coded and is a bit tricky to work with because of the way kopf initializes the operator. the current default 60 second is a sweet spot that is less likely breach rate limits while syncing secrets and triggering re-deployments reasonably quickly in most setups. will look into this when i have some time.

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

No branches or pull requests

2 participants