Chapter 3. Deploying Red Hat OpenShift Container Platform
With the prerequisites met, the focus shifts to the installation of Red Hat OpenShift Container Platform. The installation and configuration is done via a series of Ansible playbooks and roles provided by the OpenShift RPM packages.
Run the installer playbook to install Red Hat OpenShift Container Platform:
$ ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.ymlThe playbook runs through the complete process of installing Red Hat OpenShift Container Platform and reports a play recap showing the number of changes and errors (if any).
PLAY RECAP *********************************************************************************** app1.example.com : ok=233 changed=40 unreachable=0 failed=0 app2.example.com : ok=233 changed=40 unreachable=0 failed=0 app3.example.com : ok=233 changed=40 unreachable=0 failed=0 infra1.example.com : ok=233 changed=40 unreachable=0 failed=0 infra2.example.com : ok=233 changed=40 unreachable=0 failed=0 infra3.example.com : ok=233 changed=40 unreachable=0 failed=0 localhost : ok=12 changed=0 unreachable=0 failed=0 master1.example.com : ok=674 changed=161 unreachable=0 failed=0 master2.example.com : ok=442 changed=103 unreachable=0 failed=0 master3.example.com : ok=442 changed=103 unreachable=0 failed=0 Tuesday 29 August 2018 10:34:49 -0400 (0:00:01.002) 0:29:54.775 ******** =============================================================================== openshift_hosted : Ensure OpenShift router correctly rolls out (best-effort today) -- 92.44s openshift_hosted : Ensure OpenShift registry correctly rolls out (best-effort today) -- 61.93s openshift_health_check ------------------------------------------------- 53.92s openshift_common : Install the base package for versioning ------------- 42.15s openshift_common : Install the base package for versioning ------------- 36.36s openshift_hosted : Sanity-check that the OpenShift registry rolled out correctly -- 31.43s cockpit : Install cockpit-ws ------------------------------------------- 27.65s openshift_version : Get available atomic-openshift version ------------- 25.27s etcd_server_certificates : Install etcd -------------------------------- 15.53s openshift_master : Wait for master controller service to start on first master -- 15.21s openshift_master : pause ----------------------------------------------- 15.20s openshift_node : Configure Node settings ------------------------------- 13.56s openshift_excluder : Install openshift excluder ------------------------ 13.54s openshift_node : Install sdn-ovs package ------------------------------- 13.45s openshift_master : Create master config -------------------------------- 11.92s openshift_master : Create the scheduler config ------------------------- 10.92s openshift_master : Create the policy file if it does not already exist -- 10.65s openshift_node : Install Node service file ----------------------------- 10.43s openshift_node : Install Node package ---------------------------------- 10.39s openshift_node : Start and enable node ---------------------------------- 8.96s
3.1. Registry volume
The OpenShift image registry requires a volume to ensure that images are saved in the event that the registry needs to migrate to another node.
The initial installation of OpenShift will configure vSphere-volume and make it the default storage class. The registry will be installed, but it will be configured to use an EmptyDir.
After the deployment is finished, the following steps reconfigure the registry to use the vSphere-volume storage class:
cat << EOF > pvc-registry.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: vsphere-registry-storage
annotations:
volume.beta.kubernetes.io/storage-class: standard
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 30Gi
EOF
# submit the PVC
oc create -f pvc-registry.yaml
# update the volume config to use our new PVC
oc volume dc docker-registry --add --name=registry-storage -t pvc --claim-name=vsphere-registry-storage --overwrite
# rollout the new registry
oc rollout latest docker-registry
# verify the new volume
oc volume dc docker-registryThe registry volume size should be at least 30GB.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.