Deploying OpenShift Container Platform 3 on Amazon Web Services

Updated -

This reference architecture describes how to deploy and manage Red Hat OpenShift Container Platform 3 on Amazon Web Services. Red Hat OpenShift Container Platform allows for specific configuration parameters to be set to take full advantage of cloud specific features. These documents explain how OpenShift and AWS can be used together for a successful installation and deployment. Also, steps and links to a code base will be provided to allow for the installation of the exact reference architecture environment using an Amazon Web Services account.

5 Comments

In section 3.1.1 - Add/modify your organization name into the organizations list in openshift-setup.yaml

In section 4.8.1 - When logging into the OpenShift UI console, you will be prompted for your github credentials. Once logged in, you will be prompted to authorize the login on the github side, be sure to grant access on the same page prior to authorizing the login. If you don't, your application/account will not be granted into the Third-party application access policy of your organization. As a result you will not be a member of your organization and OpenShift will deny access because it is unable to match your organization membership with what it is looking for in section 3.1.1.

Video of the install is here https://vimeo.com/187092099

Hi! I've installed OSE 3.4 in AWS in a three node cluster (one master, two nodes) however three failed installs later the docker-registry POD won't run if I attach the default docker-registry NFS mount that was created I presume during the OSE installation.
Errors are ; Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "docker-registry-2-7snl7"/"default". list of unattached/unmounted volumes=[registry-storage] Then one of these: Unable to mount volumes for pod "docker-registry-2-7snl7_default(19fcf083-164c-11e7-b28c-02eccfcd045f)": timeout expired waiting for volumes to attach/mount for pod "docker-registry-2-7snl7"/"default". list of unattached/unmounted volumes=[registry-storage] then two of these: MountVolume.SetUp failed for volume "kubernetes.io/nfs/19fcd831-164c-11e7-b28c-02eccfcd045f-registry-volume" (spec.Name: "registry-volume") pod "19fcd831-164c-11e7-b28c-02eccfcd045f" (UID: "19fcd831-164c-11e7-b28c-02eccfcd045f") with: exit status 32 T

Everything about this install is vanilla, and FWIW I have another OSE 3.4 running as a single-node and that is running just fine.

I've posted over on github: https://github.com/openshift/origin/issues/13599

When I checked the permissions they looked perfectly fine, exactly the same as my single-node OSE 3.4

Any help would be greatly appreciated

Hi, if you have the OpenShift subscription, could you please open the support ticket? - https://access.redhat.com/support/

please update 3.4 to 3.5