How winsonsou/lazarus-cluster-gitops-pro works
This project is a GitOps repository designed to manage NKP Management Cluster resources using Kustomize and FluxCD. It orchestrates both workspace configurations (e.g., RBAC, projects) and cluster-level resources, including handling secrets via sealed secrets. The repository provides a GitOps workflow that applies configuration updates to a management cluster, with detailed instructions and scripts (the .sh files) to create sealed secrets for secure credential management.
And Label Main Components
• Top-Level Manifests: Include the primary Kustomization files (kustomization.yaml, workspace-kustomization.yaml, clusters-kustomization.yaml) as the entry points.
• Cluster Resources: Emphasize the structure under resources/workspaces/lazarus/cluster where various cluster configs and sealed secret scripts reside.
• External Tools & Services: Represent integrations with FluxCD (e.g., GitRepository, Kustomization CRDs), HelmRepository, and HelmRelease for installing the sealed secrets controller.
• Sealed Secrets Management: Mark the components (scripts and sealed YAML files) used to manage sensitive configuration information.
Relationships and Data Flow
• How the workspace kustomization splits into workspaces (directories like lazarus and phoenix) and then connects to the underlying workspace resource files (like lazarus-workspace.yaml).
• Dependency where the clusters kustomization “dependsOn” the workspace configuration.
Architectural Patterns and Design Principles
• GitOps Workflow: Clearly illustrate the continuous reconciliation loop provided by FluxCD and how it pulls configuration from Git.
• Separation of Concerns: Show the separation between workspace management and cluster-level management.
• Security via Sealed Secrets: Indicate the use of sealed secrets to manage sensitive credential data and include connections to the HelmRelease that installs the sealed secrets controller.
Specify Relevant Technologies & Frameworks
• Kustomize (for manifest management)
• FluxCD (GitOps controller managing the deployment, including GitRepository and Kustomization CRDs)
• Helm (via HelmRelease and HelmRepository for deploying sealed secrets)
• Sealed Secrets (for secure secret handling)
• Kubernetes (as the target environment for these resources)