Georgi Lazarov
Georgi Lazarov
the same here, you need to use nextcloud:fpm (with fpm tag) + nginx enabled
the same here but not with GCP, fixed by changing https://github.com/aquasecurity/postee/blob/main/deploy/helm/postee/values.yaml#L254 to ReadWriteMany. @simar7 why postee is needed to be sts, not deployment, is there any reason?
Nope, I got timeout `Request timeout for icmp_seq 0 .. 1 .. 2 etc` but I can open it via web browser without any problem
Yeah the same domain, I use domain name, i am testing it with public subdomain for example: esxi.example.com, also I use reverse proxy to forward the traffic to the internal...
Fixed by adding podSecurityContext: fsGroup: 1099 It should be activated by default https://github.com/aquasecurity/postee/blob/main/deploy/helm/postee/values.yaml#L37-L46 ``` podSecurityContext: fsGroup: 1099 securityContext: runAsUser: 1099 runAsGroup: 1099 ```
@simar7 please review it https://github.com/aquasecurity/postee/pull/474 . already tested with FluxCD. for example - if posteUi.existingSecret is false, it will create a secret with username & password defined into values.yaml if...
@souravsk under rego-templates dir there is a trivy-operator-slack.rego file, it should be update with the aforementioned requirements. You may also reuse trivy-jira.rego file
@souravsk it's a slack notification message
Hi @souravsk this changes wont work, you need to install Trivy Operator, which has to be integrated with Postee. Postee will receive Vulnerability reports from the Trivy Operator as json...