Matthias Bertschy
Matthias Bertschy
sometimes the synchronizer has a huge chunk of changes to push, but once this has passed it should come back to normal - this is something we should improve
yes, probably the sync configuration has changed and we were sending less data before
please bump the memory for the moment, I will look into it when I get some time
> @matthyx I'm [examining the differences between](https://github.com/kubescape/helm-charts/compare/kubescape-operator-1.18.13...kubescape-operator-1.18.14#diff-dbee05c4ed5af6518fa52ee9d2ded91a6c73640791e1a098f2be22a1f9707a27R154) versions, and the change in memory usage doesn't make sense, especially since the NodeInfo is disabled by default. Could the issue be related...
> @matthyx as I can see that you talked about storage, I don't know if it's related but the storage pod also increased a lot in term of memory usage....
storage has been updated in recent version with much better memory profiles, please try the latest helm release and reopen as needed
You cannot be assigned without being in the org... But consider as it is the case, be my guest.
@slashben maybe we should check the default list of controls?
thanks, we'll look into it
docs: - https://github.com/goharbor/pluggable-scanner-spec - https://github.com/goharbor/community/blob/main/proposals/pluggable-image-vulnerability-scanning_proposal.md examples: - https://github.com/goharbor/harbor-scanner-trivy - https://github.com/anchore/harbor-scanner-adapter