Link to recording: https://drive.google.com/open?id=12YZWFm2XcZXcxaOyCa3TDxPqBFIqadIq

Background info

Epic Goal
The user no longer needs to manually retrieve cloud provider credentials when creating secret object for Azure.

Inform user they no longer need to create a secret. If they want to do it manually, they can still follow the procedure.

New YAML:
apiVersion: v1
kind: Secret
metadata:
name: peer-pods-secret
namespace: openshift-sandboxed-containers-operator
type: Opaque
stringData:
AZURE_CLIENT_ID: "<enter value>" 1
AZURE_CLIENT_SECRET: "<enter value>" 2
AZURE_TENANT_ID: "<enter value>" 3
AZURE_SUBSCRIPTION_ID: "<enter value>" 4

Move these, along with how to retrieve them,to the config map YAML:
AZURE_REGION
AZURE_RESOURCE_GROUP

Updated configmap YAML:
apiVersion: v1
kind: ConfigMap
metadata:
name: peer-pods-cm
namespace: openshift-sandboxed-containers-operator
data:
CLOUD_PROVIDER: "azure"
VXLAN_PORT: "9000"
AZURE_INSTANCE_SIZE: "Standard_B2als_v2" 1
AZURE_INSTANCE_SIZES: "Standard_DC2as_v5,Standard_DC4as_v5,Standard_DC8as_v5" 2
AZURE_SUBNET_ID: "<enter value>" 3
AZURE_NSG_ID: "<enter value>" 4
PROXY_TIMEOUT: "5m"
DISABLECVM: "true"
AZURE_REGION: "<enter value>" 5
AZURE_RESOURCE_GROUP: "<enter value>" 6

(Day 1) Install, Configure, Acceptance Test (procedures)

Creating a peer-pod ConfigMap for Azure using the web console
Creating a peer-pod ConfigMap for Azure using the CLI

• Edit info at beginning of section to reflect changes.
• Move steps for manual retrieval of parameters.
• Update new YAML file.