Motivation
Currently, when a new customer is onboarded, the required ArgoCD configuration must be created manually. This process is repetitive and depends on following specific conventions documented internally.
To improve consistency and ensure that the onboarding process follows our GitOps standards, the bootstrap process should automatically create the necessary ArgoCD structure for new customers under firestartr-pro/argocd, following the conventions described in this documentation:
https://github.com/prefapp/gitops-k8s/blob/d87f3f899b5cdd5e1a008446513e12631840b08d/docs/internal/Argo-namespaces.md
Automating this step will help us stay prepared for future customer onboarding and ensure that every new customer environment is provisioned in a standardized way.
Description
When a new customer is added through the bootstrap process, the system should automatically:
- Create a new namespace for the customer's organization in ArgoCD.
- Generate the required configuration structure following the documented standards.
- Assign the appropriate permissions so the customer can access their namespace in our ArgoCD instance.
Expected Outcome
- Standardized ArgoCD configuration for all customers.
- Reduced manual setup during customer onboarding.
- Better alignment with our GitOps practices.
Notes
This feature focuses specifically on automating the ArgoCD namespace and access configuration as part of the customer bootstrap process.
Motivation
Currently, when a new customer is onboarded, the required ArgoCD configuration must be created manually. This process is repetitive and depends on following specific conventions documented internally.
To improve consistency and ensure that the onboarding process follows our GitOps standards, the bootstrap process should automatically create the necessary ArgoCD structure for new customers under firestartr-pro/argocd, following the conventions described in this documentation:
https://github.com/prefapp/gitops-k8s/blob/d87f3f899b5cdd5e1a008446513e12631840b08d/docs/internal/Argo-namespaces.md
Automating this step will help us stay prepared for future customer onboarding and ensure that every new customer environment is provisioned in a standardized way.
Description
When a new customer is added through the bootstrap process, the system should automatically:
Expected Outcome
Notes
This feature focuses specifically on automating the ArgoCD namespace and access configuration as part of the customer bootstrap process.