trivy-operator: "invalid character 'Q' looking for beginning of value"
Hello, after deploying trivy-operator chart we are seeing quite a lot of errors from trivy-operator
pod:
{"level":"error","ts":"2023-03-08T03:18:05Z","msg":"Reconciler error","controller":"job","controllerGroup":"batch","controllerKind":"Job","Job":{"name":"scan-vulnerabilityreport-7d6f4d5d7d","namespace":"trivy-operator"},"namespace":"trivy-operator","name":"scan-vulnerabilityreport-7d6f4d5d7d","reconcileID":"894c8f5a-0b6e-4603-a4b9-79ab34dffafa","error":"invalid character 'Q' looking for beginning of value","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:235"}
What steps did you take and what happened:
Our trivy-operator config looks like this:
trivy:
mode: ClientServer
serverURL: http://trivy-service.trivy-operator:4954
serverInsecure: true
ignoreUnfixed: true
additionalVulnerabilityReportFields: "Target,Class"
timeout: "10m0s"
resources:
requests:
cpu: 200m
memory: 512Mi
limits:
cpu: 400m
memory: 1024Mi
trivyOperator:
scanJobCompressLogs: false
resources:
requests:
cpu: 200m
memory: 512Mi
limits:
cpu: 400m
memory: 1024Mi
operator:
rbacAssessmentScannerEnabled: false
infraAssessmentScannerEnabled: false
builtInTrivyServer: true
metricsFindingsEnabled: false
exposedSecretScannerEnabled: false
webhookBroadcastURL: "http://postee.trivy-operator:8082"
serviceMonitor:
enabled: false
Environment:
- Trivy-Operator version (use
trivy-operator version
): 0.12.0 - Kubernetes version (use
kubectl version
): 1.23.15
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 39 (22 by maintainers)
@d-mankowski-synerise thanks you for this update , I’ll take a look and update you.
Sure, no problem.
The k8s manifest we use is something like this (I didn’t deploy & test it, though)