Chapter 1. Overview
The following release notes for OpenShift Container Platform 3.5 summarize all new features, major corrections from the previous version, and any known bugs upon general availability.
1.1. Versioning Policy
OpenShift Container Platform provides strict backwards compatibility guarantees for all supported APIs, excluding alpha APIs (which may be changed without notice) and beta APIs (which may occasionally be changed in a non-backwards compatible manner).
The OpenShift Container Platform version must match between master and node hosts, excluding temporary mismatches during cluster upgrades. For example, in a 3.5 cluster, all masters must be 3.5 and all nodes must be 3.5. However, OpenShift Container Platform will continue to support older
oc clients against newer servers. For example, a 3.4
oc will work against 3.3, 3.4, and 3.5 servers.
Changes of APIs for non-security related reasons will involve, at minimum, two minor releases (3.1 to 3.2 to 3.3, for example) to allow older
oc to update. Using new capabilities may require newer
oc. A 3.2 server may have additional capabilities that a 3.1
oc cannot use and a 3.2
oc may have additional capabilities that are not supported by a 3.1 server.
Table 1.1. Compatibility Matrix
oc client may not be able to access server features.
oc client may provide options and features that may not be compatible with the accessed server.