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 AWS.

AWS

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:
AWS_ACCESS_KEY_ID: "<enter value>" 1
AWS_SECRET_ACCESS_KEY: "<enter value>" 2

Move these, along with how to retrieve them,to the config map YAML:
AWS_REGION
AWS_SUBNET_ID
AWS_VPC_ID
AWS_SG_IDS

Updated configmap YAML:
apiVersion: v1
kind: ConfigMap
metadata:
name: peer-pods-cm
namespace: openshift-sandboxed-containers-operator
data:
CLOUD_PROVIDER: "aws"
VXLAN_PORT: "9000"
PODVM_INSTANCE_TYPE: "t3.medium" 1
PODVM_INSTANCE_TYPES: "t2.small,t2.medium,t3.large" 2
PROXY_TIMEOUT: "5m"
AWS_REGION: "<enter value>" 3
AWS_SUBNET_ID: "<enter value>" 4
AWS_VPC_ID: "<enter value>" 5
AWS_SG_IDS: "<enter value>" 6

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

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

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