New sub.... a few suggestions.... if you can show the architecture design in the beginning then explain, I believe more people will get more out of it then just following instructions. We want to understand what we are building and why? Thanks.
To be a dick: i see a basic setup done manually, no best-practices. Best practices would be about security, terraform/argocd handover, creating and parameterizing terraform modules, automate the argocd installation with terraform, secrets management, team isolation and so on. It's a starting point, now you have to work on it for 6 month to create a resilient, secure, fully automated platform based on best-practices.
You can do it just without this step which changing the ClusterIP to LoadBalancer in the instructions file. After that you can reach ArgoCD by private IP address.
New sub.... a few suggestions.... if you can show the architecture design in the beginning then explain, I believe more people will get more out of it then just following instructions. We want to understand what we are building and why? Thanks.
Of course! Thank you for your feedback I will have it on mind for the next videos.
To be a dick: i see a basic setup done manually, no best-practices. Best practices would be about security, terraform/argocd handover, creating and parameterizing terraform modules, automate the argocd installation with terraform, secrets management, team isolation and so on. It's a starting point, now you have to work on it for 6 month to create a resilient, secure, fully automated platform based on best-practices.
You have your point. Of course it is just a first step.
@@nbglink i hope your all eks nodes will have work properly so i could run my applications on eks properly
What if I don't to exposed the Argo CD publicly for security reason? how can access it privately?
You can do it just without this step which changing the ClusterIP to LoadBalancer in the instructions file. After that you can reach ArgoCD by private IP address.