Skip to content

fix(ci): enable kube-linter default checks#303

Merged
KeiaiLab-PHIL merged 1 commit into
mainfrom
fix/kube-linter-enable-default-checks
Jun 10, 2026
Merged

fix(ci): enable kube-linter default checks#303
KeiaiLab-PHIL merged 1 commit into
mainfrom
fix/kube-linter-enable-default-checks

Conversation

@KeiaiLab-PHIL

Copy link
Copy Markdown
Contributor

Summary

  • Re-enable kube-linter default checks by removing doNotAutoAddDefaults: true and the empty include list.
  • Keep exclude: [] so future exceptions are explicit.
  • This prevents empty/invalid SARIF output while still surfacing chart findings through SARIF.

Validation

  • helm lint charts/mongodb-operator
  • kube-linter lint /tmp/mongodb-kube-linter-rendered --config .github/kube-linter-config.yaml --format plain now reports real PDB findings.
  • kube-linter lint ... --format sarif --output /tmp/mongodb-kube-linter.sarif writes valid SARIF 2.1.0 with 6 results.

Notes

  • The kube-linter workflow already uses continue-on-error: true for chart-level follow-up findings. The fix targets SARIF validity, not suppressing findings.

Signed-off-by: keiailab <noreply@keiailab.com>
@KeiaiLab-PHIL KeiaiLab-PHIL force-pushed the fix/kube-linter-enable-default-checks branch from d3aa76f to 156105d Compare June 10, 2026 09:43
@KeiaiLab-PHIL KeiaiLab-PHIL merged commit 3f57b13 into main Jun 10, 2026
10 checks passed
@KeiaiLab-PHIL KeiaiLab-PHIL deleted the fix/kube-linter-enable-default-checks branch June 10, 2026 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant