search

phasehq / kubernetes-secrets-operator

Securely sync secrets and environment variables with Phase in your Kubernetes cluster
GNU General Public License v3.0
5 stars 1 forks source link

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

Open dodistyo opened 1 month ago

dodistyo commented 1 month ago

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 commented 1 month ago
  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.