Node-collector pods not running on master nodes #1947
-
I have deployed trivy-operator via argocd. ---
kind: Application
metadata:
name: trivy-operator
namespace: argocd
spec:
project: default
source:
repoURL: 'https://aquasecurity.github.io/helm-charts/'
targetRevision: 0.20.6
helm:
parameters:
- name: compliance.cron
value: '0 0 * * *'
- name: compliance.reportType
value: 'all'
- name: service.headless
value: 'false'
- name: serviceMonitor.enabled
value: 'true'
- name: trivy.storageClassEnabled
value: 'true'
- name: trivy.storageClassName
value: "openebs-hostpath"
- name: trivy.storageSize
value: "10Gi"
- name: trivyOperator.scanJobTolerations
value: '[{"key": "node-role.kubernetes.io/master", "operator": "Equal", "value": "master", "effect": "NoSchedule"}]'
chart: trivy-operator
destination:
server: 'https://kubernetes.default.svc'
namespace: trivy-system
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true I can see clusterinfraassessmentreports only for my worker nodes
In the logs of the trivy-operator pod, I can see the following error: I have a master node with these values, some values were hidden with the * sign.
The syntax of the tolerations field looks correct. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 9 replies
-
I also noticed that PVC was not created for trivy-operator. |
Beta Was this translation helpful? Give feedback.
-
@xRTRx can you please share how this value, |
Beta Was this translation helpful? Give feedback.
-
@xRTRx I think I found the issue, its the additional apostrophe at the beginning and at the end of the toleration:
|
Beta Was this translation helpful? Give feedback.
-
@xRTRx thanks for this update, can we close this issue ? |
Beta Was this translation helpful? Give feedback.
Thank you, that was the issue.
I couldn't correctly set the required value in the parameters section of the ArgoCD manifest, so moved it to the values section, now it works as expected, here is my updated manifest: