Deploying Litmus Unify on Kubernetes cluster with ArgoCD

you can deploy litmus unify using argocd to ensure your kubernetes cluster is equipped with the necessary configurations and resources before you begin ensure you have argocd set up and connected to a working kubernetes cluster important notes do not enable the prune function the current version of unify may result in specific resources remaining out of sync within the argocd application these include the litmus uns creds , luns default tls and mqtt migration pods (while these limitations exist, they do not affect the overall functionality of your deployment ) it's crucial to understand that both litmus uns creds and luns default tls are essential resources and should not be removed this is why the prune function is not applicable during update or upgrade procedures as for the mqtt migration pods, they can be manually deleted once their status shows that they have completed their tasks step 1 initial setup for litmus unify deployment to deploy unify on kubernetes cluster obtain the secret yaml file from litmus via the litmus central portal create the desired working namespace (e g , uns ) in the kubernetes cluster using the kubectl cli tool command (sudo) kubectl create namespace uns assuming the secret yaml file is in your current working directory, create a kubernetes secret resource in the working namespace for example, using uns as the namespace command (sudo) kubectl create f litmusautomation uns centralportal secret yml namespace=uns ensure you have the path to a valid git repository containing the unify helm chart in the argocd applications interface, click on the +new app icon fill in the application name , project name , repository url , path , cluster url , and namespace fields, along with other desired options click the create button to initialize the application a new application card will be created in argocd click the sync button to open the synchronization screen click the synchronize button to start the synchronization process and deploy unify the application is successfully deployed when the status changes to healthy and synced step 2 updating and upgrading unify when making edits to the values yaml file or when a new version of unify is released, follow these steps to perform the update process in the values yaml file, set the secrets create flag to false and the luns createtlssecret flag to false ensure that you save the above changes along with any other edits, and then commit and push them to the git repository click the refresh button on the application card if the git repository has been updated, you will see an outofsync status click the sync button to open the synchronization screen by clicking the synchronize button, you will update unify