Update KubeAid config files and disable ArgoCD servicemonitors#39
Open
param20h wants to merge 16 commits intoObmondo:mainfrom
Open
Update KubeAid config files and disable ArgoCD servicemonitors#39param20h wants to merge 16 commits intoObmondo:mainfrom
param20h wants to merge 16 commits intoObmondo:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a new ArgoCD "root app" pattern for managing a local Kubernetes cluster (
my-local-cluster). It sets up hierarchical ArgoCD Application CRs to deploy and manage core infrastructure components (such as ArgoCD itself, cert-manager, sealed-secrets, and kube-prometheus), and provides the associated configuration and secrets for GitOps workflows. The changes also include initial values and configuration files for these apps, as well as sealed secrets for repository authentication.ArgoCD Application Definitions and Management
rootArgoCD Application inroot.yamlto serve as the entry point, which manages the other application manifests in the cluster. This enables a hierarchical, GitOps-driven deployment model. (k8s/my-local-cluster/argocd-apps/templates/root.yaml)argocd,cert-manager,sealed-secrets,secrets, andkube-prometheus, each specifying their sources, sync policies, and deployment order via labels. (k8s/my-local-cluster/argocd-apps/templates/argocd.yaml,cert-manager.yaml,sealed-secrets.yaml,secrets.yaml,kube-prometheus.yaml) [1] [2] [3] [4] [5]Chart.yamlto define the Helm chart for the root app. (k8s/my-local-cluster/argocd-apps/Chart.yaml)Configuration and Values
argocd,cert-manager, andsealed-secretsto customize Helm chart deployments. (values-argocd.yaml,values-cert-manager.yaml,values-sealed-secrets.yaml) [1] [2] [3]k8s/my-local-cluster/kubeaid-bootstrap-script.general.yaml)my-local-cluster-vars.jsonnetwith cluster-specific variables for resource requests, Prometheus configuration, and feature toggles. (k8s/my-local-cluster/my-local-cluster-vars.jsonnet)Sealed Secrets for GitOps
kubeaidandkubeaid-configGit repositories, storing encrypted SSH keys and repository URLs as Kubernetes secrets. (k8s/my-local-cluster/sealed-secrets/argocd/repo-kubeaid.yaml,repo-kubeaid-config.yaml) [1] [2]These changes lay the foundation for a reproducible, GitOps-managed local cluster setup, with secure repository access and modular, hierarchical application management.