Update:

Jan Hellar and I were working on installation of the community cluster replacement. We chose 2 approaches:

1. Install 2-node cluster manually from the beginning.
Reason: To have the cluster configured according to latest OpenShift docs.
Result:

• https://community.aerogear.org:8443/console - cannot be resolved from RH network atm - David Kirwan Mark Freer Jesse Sarnovsky, do you guys have some idea what's causing this?
• default user: developer/developer, ping me to get credentials for admin user
• todo:
  • Resolve the issue with DNS
  • Add valid SSL cert
  • Replace NFS storage with EBS

2. Use fhcap (cluster-create pipeline to prepare aws nodes for us and install OpenShift on provided nodes (3 in total) manually.

• in progress

Mark Freer, I believe we can delete the previous community cluster now since it's in a bad state again, nobody's using it (afaik) and the new one could serve as a replacement now (hopefully we will resolve the DNS issue quickly).