Cloud Provider CLI Setup

• Follow the instructions here to install your AWS cli.
• Verify that the cli has been added to your $PATH
• Follow the instructions here to configure your cli and connect it to your aws console
• Verify that your cli has been properly configured by running

aws configure list

You should see a set of values that looks like this:

Name                    Value             Type    Location
      ----                    -----             ----    --------
   profile                <not set>             None    None
access_key     ****************RUG2 shared-credentials-file    
secret_key     ****************hJUU shared-credentials-file    
    region                us-east-2      config-file    ~/.aws/config

If you are deploying to an AWS account with SSO enabled, you'll need to pass that specific AWS profile to the Plural CLI, or it won't be able to create resources on your behalf. You can do this with the following two steps:

1. Run export AWS_PROFILE=profile_name to set this variable for your terminal session.
2. Run aws sso login to open your relevant SSO auth page and log in.

If you need to update your AWS CLI for any reason, make sure to run plural wkspace kube-init to regenerate your kubeconfig to be compatible with the changes. This will be required if you're on a new machine, were using a different Kubernetes cluster, or if the kubeconfig has stale credentials.

• Follow the instructions here to install the gcloud cli.
• Verify that the cli has been added to your $PATH
• Create a new project in gcp via the cli:

gcloud projects create example-project-name

• Enable the Kubernetes Engine API for the project you just created.
• Enable the Google DNS API for the project you just created.
• Run gcloud init and follow the prompts to configure the gcloud cli and connect it to the project you just created.
• Verify that your cli has been properly configured. It should look something like this. Make sure that your active configuration is set to the project you just created.

> gcloud config list
[compute]
region = us-east1
zone = us-east1-b
[core]
account = yirenlu92@gmail.com
disable_usage_reporting = True
project = example-project-name

Your active configuration is: [example-project-name]

• If you have multiple projects in GCP and previously have configured your gcloud cli to point to a different project, run

gcloud auth application-default login

to reset the application default credential and re-authorize the browser. Failure to do this could result in project requested not found errors further along.

• Follow the instructions here to install your Azure CLI.
• Follow the instructions here to sign into your Azure CLI.

Service Account Permissions

When deploying via GCP, you may run into a Terraform error around permissions. Plural will need to create a various set of resources in order to make sure that your Kubernetes cluster is configured correctly. We recommend attaching the following permission roles to the service account associated with your CLI or Cloud Shell:

• owner
• storage.admin

Follow these steps to authorize your GCloud CLI with a new or existing Service Account.

No special permissions necessary, but as mentioned above, providing Plural Administrator access will prevent issues around application specific requirements.

No special permissions necessary, but as mentioned above, providing Plural Administrator access will prevent issues around application specific requirements. Make sure you're specifically providing Administrator access for the resource group you're deploying Plural into.