OpenShift Container Platform 3 to 4 oversubscriptions during cluster migration explained.
OpenShift 4 introduced a new software licensing SaaS service on cloud.redhat.com that dramatically decreases the amount of operational time a customer must spend subscribing their OpenShift clusters. This new feature is specifically useful during a OpenShift 3 to OpenShift 4 migration.
Customers will log into This content is not included.This content is not included.https://cloud.redhat.com/openshift/install with their Red Hat registered account. Generate a pull token as explained on the site. Install OpenShift 4. They can build the same number of clusters they would have been entitled to build if their subscriptions were not currently occupied. For the purposes of a v3 to v4 workload migration, those clusters will work and receive software updates and support from Red Hat, without an allocated subscription, for however long Red Hat and the customer decide their migration should take. Should a customer need more time than the agreed upon migration period, Red Hat will notify the customer, via their local Red Hat team, 3 months prior to ending the oversubscription period so that alternative plans can be made or the period of over usage extended. When the customer logs back into cloud.redhat.com, they will see all these new OpenShift 4 clusters in the new OpenShift Cluster Manager portal. On successful completion of migration, at the point of decommissioning a v3 cluster, they will select a v4 cluster and connect a subscription to it. No more subscribing each node one at a time. Every 24 hours, cloud.redhat.com will justify the subscription and remove or add units as needed based on whether or not the customer added or removed nodes from the cluster. This process works great for RHEL CoreOS driven OpenShift 4 clusters. If the customer is not migrating to RHEL CoreOS and instead attaching RHEL7 nodes to their OpenShift 4 cluster, the RHEL subscription manager would be involved. To enable double subscriptions for such a situation, the customer will need to contact their local Red Hat team to request additional subscriptions that RHEL subscription manager will understand.
Customers are within the rights of their existing OpenShift software entitlements to overscribe while they migrate workloads from OpenShift 3 to OpenShift 4 if they are faithfully and with intention moving to OpenShift 4 and decommissioning OpenShift 3. During this period of oversubscription, the customer will receive the level of support paid for on the OpenShift 3 clusters as well as being eligible to receive software updates.