Closed vemonet closed 3 years ago
Issue experienced with steps IP resolution:
https://github.com/argoproj/argo/issues/1272#issuecomment-520756631
Changes now in https://github.com/MaastrichtU-IDS/argo
Thing that will need to be carried on later: https://github.com/argoproj/argo/issues/1273
At the moment working on deploying Argo on a different namespace than argo
Doc on install: https://github.com/argoproj/argo-cd/tree/master/manifests We should go with namespace-install.yaml
Best practices: https://argoproj.github.io/docs/argo-cd/docs/user-guide/best_practices.html
https://blog.argoproj.io/the-state-of-kubernetes-configuration-management-d8b06c1205
https://github.com/argoproj/argo/blob/master/manifests/namespace-install/kustomization.yaml
Using Ansible: https://itnext.io/provisioning-argo-on-openshift-with-ansible-and-kustomize-340a1fda8b50`
Python client: https://github.com/CermakM/argo-client-python
Drill on Kubernetes: https://github.com/Agirish/drill-containers/tree/master/kubernetes
MacOS environment: https://medium.com/@mo_keefe/a-kubernetes-development-workflow-for-macos-8c41669a4518
Install Argo from amalic repository on the new cluster: https://github.com/amalic/argo/