Description

Initial investigation of what are the issues when BC is deployed in Openshift 4.2

Log

• OCS 4.2 will be released in November.
• OCS 4.2 only supports AWS and VMWare right now.
• OpenShift Container Storage 4.2 (planned to be released in November), which will be compatible with OCP 4.2, and will provide Ceph/Rook-based storage and will replace Gluster as the underlying implementation technology.
• It seems that CRC (current version) doesn't include ceph.
• We need 4.2 Version (at least beta) of CRC and Full installation because Ceph seems to have RWX feature in that version, but not in previous ones.
• Ceph is the new default storage for Openshift 4.2. For 3.11 we are using GlusterFS and we need to understand differences and analyze how that impact on actual implementation. The main risk here is that right now (as far as I could see) only implements ReadWriteOnce that is a mechanism about how pods read and write information into persistent storage. ReadWriteOnce means that only one pod can read or write in a persistence volume at a time. https://docs.openshift.com/container-platform/3.3/architecture/additional_concepts/storage.html#pvc-access-modes

Risks

• Right now, not having an environment to test next OCP + OCS release is a risk
• Only supported configuration for OCS is AWS or VMWare is also a Risk. We also will need Openstack as supported configuration, or having a solution for gluster deprecation.

Env Specs

3 t2.xlarge AWS instances
T2.xlarge:

• 4 vCPUS
• 16Gb RAM

Next Steps

• Prepare a AWS environent to run OCP4.2 + OCS 4.2