SergeyBear

I tried to solve this problem by myself but I'm not very familiar with python, so it looks littlebit clumsy :-) Here is a diff [zabbix-api.diff.txt](https://github.com/r0bj/ansible-zabbix-api/files/206066/zabbix-api.diff.txt)

With this patch following variables can be used to specify zabbix-agent and jmx ports for remote host: zabbix-api: ... port1=10050 port4=12345 ... May be it'll help someone

Seems to work fine on latest kaniko 1.8.1 with `GIT_USERNAME` and `GIT_PASSWORD` env vars

Hello! The same problem with Ansible Resource Model - when trying to get nodes from ansible, it runs some ansible task on localhost with sudo (of course, it does not...

Hi there! Got the same problem with OOMKilled, but in my case, `scan-vulnerabilityreport-*` pod gets killed almost every time and each time it was during DB downloading process: ``` kubectl...

@chen-keinan At the begining I used fresh minikube cluster with 3 cpus and 6 gigs of RAM, then deployed trivy-operator and dummy nodejs app on it and started to get...

@chen-keinan sorry, forgot to mention - it appears even on single scan job. After increasing trivy limits - OOM is gone and reports completed with no errors. P.S. It is...

@chen-keinan deployed trivy-server and set trivy-operator in ClientServer mode: * with 500M memory limit `scan-vulnerabilityreport-*` pod gets killed with empty logs * with 1500M memory limit `scan-vulnerabilityreport-*` pod completes fine;...

@knqyf263 I'm using trivy-operator 0.1.9 that uses trivy 0.30.0 image

1 gig limit is too low. I managed to get rid of OOMKilled only with 1.5 gig memory limit, if you have enough free memory in cluster of course