Tenants
Documentation about Platform Tenants for managing ArgoCD deployments to Kubernetes clusters.
Overview
The Tenants section contains GitOps configurations for deploying applications to Kubernetes clusters via ArgoCD. Each tenant represents a set of environments managed by ArgoCD, with configurations stored in Git as the single source of truth.
Code Repository
The Tenants source code is available on GitLab:
Repository: https://gitlab.com/welance/platform/tenants
Available Tenants
- Welance Non-Production - GitOps configurations for non-production Kubernetes clusters
- Welance Production - GitOps configurations for production Kubernetes clusters
How Tenants Work
Each tenant folder contains:
- Environment Folders: Each subfolder (e.g.,
management,develop,staging) represents a distinct environment - Project Configurations: Each project has its own folder with Helm values and environment variables
- ArgoCD Integration: ArgoCD monitors these folders and syncs changes to Kubernetes clusters
- GitOps Workflow: Changes are made in Git, and ArgoCD automatically deploys them
Getting Started
To understand how tenants are structured and used:
- Review the Welance Non-Production documentation for non-production environments
- Review the Welance Production documentation for production environments
- Understand the environment structure and configuration files
- Learn how CI/CD pipelines interact with tenant configurations