Update structure for Flux 2.7 #121
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces major improvements to the Flux-based GitOps setup, focusing on enhanced artifact management, improved Helm release failure handling, and updated documentation. The main changes include switching to OCI-based helm charts, updating cluster configuration to use
ArtifactGenerator, modernizing Helm release definitions, and refining the documentation to reflect these updates.Artifact and Source Management:
ArtifactGeneratorresources in each cluster (artifacts.yaml) to split the monorepo into independentinfrastructureandappsartifacts, enabling more granular reconciliation and improved scalability. Kustomizations now useExternalArtifactsources instead of directly referencing the Git repository.Helm Release and Repository Handling:
HelmRepositorytoOCIRepository.ingress-nginxrelease by enabling the admission webhook with cert-manager integration.Cluster Configuration:
Documentation Updates:
README.mdto reflect the new minimum Kubernetes version, updated example manifests, and clarified cluster setup, artifact generation, and reconciliation flows.CI and Tooling Updates:
Fix: #115
Fix: #102