Hey everyone! I have two Kubernetes clusters: one where ArgoCD is installed (let's call it Cluster A) and another one (Cluster B) that I've connected to Cluster A by adding a secret with the 'argocd.argoproj.io/secret-type: cluster' label. The connection to Cluster B seems fine, but I'm having trouble deploying Helm charts from Cluster A to Cluster B. I'm currently using the Application kind to deploy Helm charts to Cluster A without issues, but when I set up an application for Cluster B, it only deploys the Application CRD and does not actually deploy the Helm chart. Is there a way to deploy Helm charts across both clusters using a single ArgoCD instance? Any advice would be greatly appreciated!
3 Answers
Definitely check the service account in Cluster B after adding it to ArgoCD. Also, project names can be a hassle. If you're using the same name like 'default' for two apps, it might cause issues. If you can’t switch to ApplicationSets, create two separate applications for your services with distinct destination names, and that should solve the problem without any issues!
You should really consider using ApplicationSets for handling deployments across multiple clusters. It simplifies the process. If it's not an option right now, you need to ensure that your application manifests are still defined in Cluster A, and just set the target to Cluster B. Remember, Cluster A will handle all the deployment tasks.
You really shouldn't create applications directly in Cluster B. Instead, keep the applications in Cluster A and just target them toward Cluster B. ApplicationSets provide a nice long-term solution, but for now, focus on how you’re structuring your applications and clusters.
Absolutely! Managing everything from Cluster A is the way to go. It just makes deployment smoother.