charts VS helm-tiller

We use Helm charts for both Rasa-X and Chatwoot, latter of which was built by us. Helm allows us to have a standard way to deploy the application instead of a lot of YAML files which need modification every time there's an update.

deploy-job: stage: deploy #before_script: [] #image: registry.gitlab.com/gitlab-org/cloud-deploy/aws-base:latest # see the note below script: - apt-get update #- apt install git-all -y - curl -k -F "model=@models/$CI_COMMIT_SHORT_SHA.tar.gz" "http://rasax-url.com/api/projects/default/models?api_token=$RASAXTOKEN" - echo "Application successfully deployed." - aws eks update-kubeconfig --name ${EKS_CLUSTER_NAME} - curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash - helm plugin install https://github.com/rimusz/helm-tiller --kubeconfig=$HOME/.kube/kubeconfig - helm repo add rasa-x https://rasahq.github.io/rasa-x-helm - helm upgrade rasa rasa-x/rasa-x -n rasa --set app.name=$CI_REGISTRY/weunlearn/wulu2.0/rasa_actions --set "app.tag=stable" --reuse-values # Redeploys the kubernetes deployment with a new image name while reusing already existing values rules: - if: '$CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == "main"'