Multi Cluster*

* 📢 Please notice that this feature is on Tech Preview

This page explains how to enable the possibility to deploy your applications or services in more than one cluster and environment at the time

GitHub Actions

1. In the main branch you will edit the YAML file named .github/workflows/github-ci.yaml

2. In the github-ci.yaml file search for the Environments section, you will find it like this:

 # Environments:
 # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)

3. Bellow the section title, add the following configuration and change the values as you need:

warning

Bearing in mind that if you choose the options full-with-drp, full, mid or minimal all the environments encompassing these groups must be available in the cluster in which you are going to deploy.
If not, you can choose the available option and ShamanOps will deploy in all the available environments

     # Environments:
     # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)
       environments: 'available'

4. In the github-ci.yaml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

5. Bellow the section title, add the following configuration and change the values as you need:

info

Please note that if you performed a classic installation of ShamanOps, that cluster is identified as main, to deploy in that cluster, you must add the main tag in this list.

 # Multicluster
      multiclusterTag: "main, violet, pink, green"

6. In the github-ci.yaml file search for the Secrets section, you will find it like this:

#-------------------------------------------------------------------------------------------
    secrets:

7. Bellow the section title, add the following configuration and change the values as you need:

     shamanops_argocd_dev_plus_token: ${{ secrets.shamanops_argocd_dev_plus_token }}
     shamanops_argocd_stg_plus_token: ${{ secrets.shamanops_argocd_stg_plus_token }}
     shamanops_argocd_prod_plus_token: ${{ secrets.shamanops_argocd_prod_plus_token }} 

8. Commit and enjoy! ✨

GitLab CI

1. In the main branch you will edit the YAML file named .github/workflows/github-ci.yaml

2. In the .gitlab-ci.yaml file search for the Environments section, you will find it like this:

 # Environments:
 # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)

3. Bellow the section title, add the following configuration and change the values as you need:

warning

Bearing in mind that if you choose the options full-with-drp, full, mid or minimal all the environments encompassing these groups must be available in the cluster in which you are going to deploy.
If not, you can choose the available option and ShamanOps will deploy in all the available environments

  # Environments:
    # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)
    environments: 'available'

4. In the .gitlab-ci.yaml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

5. Bellow the section title, add the following configuration and change the values as you need:

info

Please note that if you performed a classic installation of ShamanOps, that cluster is identified as main, to deploy in that cluster, you must add the main tag in this list.

 # Multicluster
   multiclusterTag: 'main, violet, pink, green'

6. Commit and enjoy! ✨

Azure DevOps

1. In your Azure Repo's main branch you will edit the YAML file named azdevops-ci.yml

2. In the azdevops-ci.yml file search for the Environments section, you will find it like this:

 # Environments:
 # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)

3. Bellow the section title, add the following configuration and change the values as you need:

warning

Bearing in mind that if you choose the options full-with-drp, full, mid or minimal all the environments encompassing these groups must be available in the cluster in which you are going to deploy.
If not, you can choose the available option and ShamanOps will deploy in all the available environments

  # Environments:
  # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)
  - name: environments
    value: 'available'

4. In the azdevops-ci.yml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

5. Bellow the section title, add the following configuration and change the values as you need:

info

Please note that if you performed a classic installation of ShamanOps, that cluster is identified as main, to deploy in that cluster, you must add the main tag in this list.

  # Multi Cluster
  - name: multiclusterTag
    value: 'main, violet, pink, green'

6. Commit and enjoy! ✨

Bitbucket Pipelines

1. In the main branch you will edit the YAML file named .bitbucket/envs.yaml

2. In the .bitbucket/envs.yaml file search for the Environments section, you will find it like this:

# Environments:
# full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)

3. Bellow the section title, add the following configuration and change the values as you need:

warning

Bearing in mind that if you choose the options full-with-drp, full, mid or minimal all the environments encompassing these groups must be available in the cluster in which you are going to deploy.
If not, you can choose the available option and ShamanOps will deploy in all the available environments

  # Environments:
  # full-with-drp (dev/stg/prod/drp) | full (dev/stg/prod) | mid (stg/prod) | minimal (prod) | available (multicluster)
  environments="available"

4. In the .bitbucket/envs.yaml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

5. Bellow the section title, add the following configuration and change the values as you need:

info

Please note that if you performed a classic installation of ShamanOps, that cluster is identified as main, to deploy in that cluster, you must add the main tag in this list.

  # Multi Cluster
  multiclusterTag='main, violet, pink, green'

6. Commit and enjoy! ✨

Usage

Helpful Information

How does the available environment works?

This option is designed so that the application or service is deployed only in the environments that each tag has available, considering that not all tags have available all environments.
In this screen example: the cashing app application is deployed in the violet, pink and green clusters using the available tag.
As a result the cashing app application will be displayed only on the indicated tags and in the available environments

In case you have any question or doubt please contact us at support@shamanops.com