OpenShift 4.4: Getting it Right - OLM Improvements
May 1, 2020 | by
Adding new functionality to your OpenShift cluster has always been easy. In fact, it's as easy as discovering and installing operators from the embedded OperatorHub in the OpenShift Web Console. To keep this process as simple as possible, operator developers can now specify exactly what namespace their operator should be installed to. The OpenShift Web Console then suggests that namespace as a default when installing. And if it doesn’t already exist, the OpenShift Web Console will create it for you right from the installation flow—while letting you know, of course. So with that said, let's take a look at how it all works.
Installing an operator to a predefined namespace
Certain operators benefit from being installed to a particular namespace, which has previously been conveyed through that operator’s documentation. While this has been a fine approach, operator developers can now encode that information into their operator for even easier installation by the cluster admins.
As you can see here, this user is installing the Cluster Logging operator which indicates it has a recommended installation namespace of openshift-logging. This namespace is selected as the installation namespace by default, allowing admins to quickly move through the operator installation process and get to logging (or whatever features the operator may enable).
In this particular cluster, the openshift-logging namespace doesn’t yet exist, and the console indicates that it will be created for the operator to be installed in. This is just one more way the install process is simplified.
The recommended installation namespace is just that: a recommendation. If an admin needs to install the operator to another namespace, it’s just as easy as flipping the toggle and choosing from an existing namespace.
Monitoring a new installation namespace
Operator developers may also suggest that admins allow the namespace their operator is installed in to be monitored by logging, which is helpful for keeping track of metrics exposed by the operator. This option is presented right along with the newly created namespace, which is deselected by default so that you can deliberately opt in.
Making sure operators are easy to find and install is a top priority for OperatorHub in OpenShift, and we are continuing to work towards that goal with features like this that fast track the installation process. Expect more features to come that offer even more ways to find operators that are right for you, and more clarity into the operator installation process.
If you are just getting started with OpenShift or want to try these features now, visit the newly revamped Try OpenShift site to get instant access to a cluster. If you’d like to learn more about what the OpenShift design team is up to, check out our github design repo, or if you are interested in providing any feedback on any of the new 4.4 features or have suggestions for the future, please take this brief 3-minute survey.
We are pleased to announce the release of OpenShift Service Mesh 2.3. OpenShift Service Mesh is based on the Istio project, with Kiali as the management console for Service Mesh, and is included and ...
Are you working with bare metal clusters and looking for a timing and synchronization solution for your containerized workloads? The Silicom Time Sync (STS) Operator was just released as a Certified ...