What If You Need Two ArgoCD Instances in One EKS Cluster?
The article discusses the implementation of two ArgoCD instances within a single Amazon EKS cluster to support different teams. It highlights the challenges of maintaining isolation between the instances while sharing resources like the AWS Application Load Balancer. The author outlines the architecture, goals, and the use of AWS Cognito for authentication in this setup.
- ▪The scenario involves a Platform Team managing infrastructure components and Application Teams deploying business applications.
- ▪The architecture allows for two ArgoCD instances to run in separate namespaces within the same EKS cluster.
- ▪AWS Cognito is used for authentication to automate user management and eliminate manual setup.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1212088) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } POTHURAJU JAYAKRISHNA YADAV for AWS Community Builders Posted on May 30 What If You Need Two ArgoCD Instances in One EKS Cluster? #aws #kubernetes #argocd #terraform Most ArgoCD tutorials start the same way: Deploy ArgoCD. Connect a Git repository. Create an Application. Done.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
