gitops-repo-audit

You can audit Flux CD GitOps repositories by running static scans on local manifests to validate Kubernetes schemas, detect deprecated Flux APIs, and review RBAC and secret management. This generates a prioritized report with actionable remediation steps.

The best way to check for deprecated Flux API versions is by performing static scans of your local repository files. This process detects outdated Flux API versions and provides specific migration guidance to update your GitOps configuration.

Validating Kubernetes manifests in a Flux repo uses dependencies like kustomize and kubeconform, along with awk, flux, and yq. These tools enable static schema validation against Kubernetes OpenAPI schemas and Flux CRDs.

You can review multi-tenancy and RBAC configurations for Kubernetes GitOps repositories. The audit assesses RBAC, multi-tenancy, secret management, and source authentication to improve your security posture across monorepo and multi-repo patterns.

The GitOps audit workflow supports both monorepo and multi-repo Flux patterns. It applies static scanning to clusters of Flux resources within these structural patterns to enforce API compliance and assess security best practices.

Validating Kubernetes OpenAPI schemas before merging Flux CD changes ensures manifests are correctly structured and compliant. Pre-merge validation catches security issues, deprecated APIs, and RBAC misconfigurations early in the development lifecycle.