1.3. Notable technical changes
OpenShift Container Platform 4.5 introduces the following notable technical changes.
Operator SDK v0.17.2
OpenShift Container Platform 4.5 supports Operator SDK v0.17.2, which introduces the following notable technical changes:
-
The
--crd-versionflag was added to thenew,add api,add crd, andgenerate crdscommands so that users can opt in tov1CRDs. The default setting isv1beta1.
Ansible-based Operator enhancements include:
- Support for relative Ansible roles and playbooks paths in the Ansible-based Operator Watches files.
- Event statistics output to the Operator logs.
Helm-based Operator enhancements include:
- Support for Prometheus metrics.
terminationGracePeriod parameter support
OpenShift Container Platform now properly supports the terminationGracePeriodSeconds parameter with the CRI-O container runtime.
/readyz configuration for API server health probe
All OpenShift Container Platform 4.5 clusters using user-provisioned infrastructure must be configured to use the /readyz endpoint for API server health checking to remain supported. Any clusters using user-provisioned infrastructure installed on versions prior to OpenShift Container Platform 4.5 must be reconfigured to use /readyz.
Clusters using user-provisioned infrastructure without /readyz configured can suffer from API outages when the API server restarts. The API server can restart after events such as configuration changes, certificate updates, or control plane machine reboots. The load balancer must be configured to take a maximum of 30 seconds from the time the API server turns off the /readyz endpoint to the removal of the API server instance from the pool. Within the time frame, the /readyz endpoint must be removed or added, depending on whether it returned an error or became healthy. The readiness check is recommended to probe every five or 10 seconds, with two consecutive successful requests to become healthy and three consecutive failed requests to become unhealthy.
For more information, see the network topology requirements in the user-provisioned infrastructure installation documentation for your cloud provider.
Binary sha256sum.txt.sig file has been renamed for OpenShift Container Platform releases
The sha256sum.txt.sig file included in OpenShift Container Platform releases has been renamed to sha256sum.txt.gpg. This binary file contains a hash of each of the installer and client binaries, which are used to verify their integrity.
The renamed binary file allows for GPG to correctly verify sha256sum.txt, which was not possible previously due to naming conflicts.
