blumeops/argocd/manifests/prowler/kustomization.yaml
Erich Blume 7c1cd11e45
All checks were successful
Build Container / detect (push) Successful in 3s
Build Container / build-dagger (prowler) (push) Successful in 36s
Upgrade Prowler to 5.23.0, remove registry workaround (#336)
## Summary

- Upgrade Prowler from 5.22.0 to 5.23.0
- Remove the `enumerate-images` init container workaround from `cronjob-image-scan.yaml`
- Use native `--registry` and `--image-filter` flags now that upstream fix (PR prowler-cloud/prowler#10470) is released

The init container was a workaround for prowler-cloud/prowler#10457 where `--registry` args weren't forwarded to the provider constructor. We wrote the fix, it was merged, and v5.23.0 includes it.

## Test plan

- [ ] Build new container (`mise run container-release prowler 5.23.0`)
- [ ] Update kustomization.yaml with new image tag
- [ ] Sync prowler ArgoCD app from branch
- [ ] Manually trigger image scan job and verify `--registry` works natively
- [ ] Verify CIS and IaC scan cronjobs still work

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #336
2026-04-14 13:45:28 -07:00

29 lines
605 B
YAML

---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: prowler
resources:
- serviceaccount.yaml
- rbac.yaml
- pv-nfs.yaml
- pvc.yaml
- cronjob.yaml
- cronjob-image-scan.yaml
- cronjob-iac-scan.yaml
configMapGenerator:
- name: prowler-mutelist
options:
disableNameSuffixHash: true
files:
- mutelist/apiserver.yaml
- mutelist/control-plane.yaml
- mutelist/core-pod-security.yaml
- mutelist/manual-node-checks.yaml
- mutelist/rbac.yaml
images:
- name: registry.ops.eblu.me/blumeops/prowler
newTag: v5.23.0-d05b503