-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Product / Portfolio Work
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Complete a list of requirements to include feature enhancements and support specific configuration modifications that will enable iBM ROKS to migrate to OVN-Kubernetes as the default CNI implementation.
Goals (aka. expected user outcomes)
IBM ROKS' default CNI will be OVN-Kubernetes.
Requirements (aka. Acceptance Criteria):
- See the following document.
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | |
| Classic (standalone cluster) | |
| Hosted control planes | |
| Multi node, Compact (three node), or Single node (SNO), or all | |
| Connected / Restricted Network | |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
| Operator compatibility | |
| Backport needed (list applicable versions) | |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
| Other (please specify) |
Use Cases (Optional):
As a cluster administrator, deploy all new ROKS Clusters using OpenShift's default OVN-Kubernetes networking plug-in with no appreciable loss of functionality, operation or security.
Questions to Answer (Optional):
Out of Scope
- Live or Limited Live Migration from the previous 3rd-party CNI plug-in to OVN-Kubernetes
Background
IBM ROKS has long standardized on a 3rd-party CNI implementation. In that time, the OpenShift's default CNI, OVN-Kubernetes, has matured and today provides significant advantages. In order to migrate to OVN-Kubernetes, ROKS has a set of feature and configuration requirements that remain in effect regardless of CNI, and need to be supported by OVN-Kubernetes.
