At this point, you are ready to perform the OpenShift installation outlined here and begin at Step 3: Download the Installer.
[~]$ openshift-install-linux-amd64 create install-config
? SSH Public Key /home/user_id/.ssh/id_rsa.pub
? Platform aws
? Region us-east-1
? Base Domain openshiftcorp.com
? Cluster Name test
? Pull Secret [? for help][~]$ openshift-install-linux-amd64 create cluster
INFO Waiting up to 30m0s for the Kubernetes API...
INFO API v1.11.0+85a0623 up
INFO Waiting up to 30m0s for the bootstrap-complete event...
INFO Destroying the bootstrap resources...
INFO Waiting up to 10m0s for the openshift-console route to be created...
INFO Install complete!
INFO Run 'export KUBECONFIG=/home/user/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI.
INFO The cluster is ready when 'oc login -u kubeadmin -p XXXX' succeeds (wait a few minutes).
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.test.openshiftcorp.com
INFO Login to the console with user: kubeadmin, password: XXXXIn Route53, there will be a new, private hosted zone (for internal lookups):
In EC2, there will be 6 running instances:
The relationship of the EC2 instances, elastic load balancers (ELBs) and Route53 hosted zones is as depicted:
The nodes within the VPC utilize the internal DNS and use the Router and Internal API load balancers. External/Internet access to the cluster use the Router and External API load balancers. Nodes are spread equally across 3 availability zones.
The OpenShift console is available via the kubeadmin login provided by the installer:
