Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Trivy-server missing explicit apiVersion and kind from volumeclaimtemplate #1206

Closed
jemag opened this issue May 4, 2023 · 0 comments · Fixed by #1207
Closed

Trivy-server missing explicit apiVersion and kind from volumeclaimtemplate #1206

jemag opened this issue May 4, 2023 · 0 comments · Fixed by #1207
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jemag
Copy link
Contributor

jemag commented May 4, 2023

What steps did you take and what happened:

  1. Enable trivy-server in the helm chart values
  2. Deploy trivy-operator using the helm chart
  3. Notice an infinite sync loop in Argo CD because the apiVersion and kind is missing from the VolumeClaimTemplates:
    image

What did you expect to happen:
apiVersion and kind is specified and ArgoCD is not trying to continuously resolve the difference

Environment:

  • Trivy-Operator version (use trivy-operator version): Helm chart 0.13.2
  • Kubernetes version (use kubectl version): v1.25.6
  • OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Ubuntu 22.04.2 LTS
@jemag jemag added the kind/bug Categorizes issue or PR as related to a bug. label May 4, 2023
@jemag jemag mentioned this issue May 4, 2023
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: specify trivy-server persistent volume claim for argocd sync jemag/trivy-operator
1 participant
@jemag