Using Third Party Network Operators with OpenShift
This section outlines the requirements and steps for integrating third-party networking providers with the OpenShift installer.
Network Operators are a special breed because they are required to be functional very early on during installation. OpenShift 4 has a facility for injecting custom objects at install time. In this case, we will use it to install a compliant network operator.
Network operators also need to consume and update certain special objects. This is how they inform cluster components of the current network status.
A critical goal of this is to be able to update and manage the networking components over time. Therefore, the new network-operator must transition to OLM ownership once the cluster is running and OLM is installed.
Requirements for OpenShift-compliant network operator
At install-time, the installer will create any manifest files in mycluster/manifests/. So, copy all manifests needed to install your operator to that directory. See Appendix A - CNI Operator manifests for examples.
openshift-install create cluster --dir=mycluster
This will deploy your cluster and apply the manifests of your CNI operator, leaving the Operator running but unmanaged.
Transition your operator to OLM ownership.
Create OperatorGroup in the namespace of the operator - Appendix C
Create subscription pointing to ISV catalog source and the desired operator - Appendix D
Verify that a ClusterServiceVersion object referring to your Operator is created
Verify that the resources now have owner references to OLM