In every OpenShift release, we make it a priority to implement work that directly relates to customer feedback. For OpenShift 4.8, we focused on improving the usability of the log toolbar, introduced a unified way to stock install custom domains for routes, and added Kata containers to the console via tech preview.

We designed and improved OpenShift 4.8 based on feedback from OpenShift users just like you. Your feedback helps improve user experiences and influence the future of Red Hat products. To play a part in future OpenShift releases, complete our current Breadcrumbs usability activity or sign up to become a participant in future research endeavors.

Let’s take a closer look at the requests for enhancements (RFEs) we made for 4.8.

Enhancements to the Log Toolbar

What we heard: Troubleshooting is hard. When viewing the pod logs tab with a selected container, customers need the ability to view past logs if they are available for the container to troubleshoot more effectively. In addition, customers need to be able to wrap lines to easily scan information.

How we responded: When we know that the container has restarted at least once, we now allow users to view the previous log. We are limited to showing one past log due to the Kubernetes API.

When viewing the pod logs, we now surface a drop-down, allowing users to view either the current log or the previous log for a container. Selection will be disabled if a previous log is not available, and users can learn why by opening a corresponding tooltip.

We also added the ability to wrap lines, which we previously supported in OpenShift 3.

Expect more improvements around the log toolbar to come in the future.

Single Point of Configuration for Custom Domains

What we heard: Some customers do not  allow wildcard serving certificates for the OpenShift ingress to use, so they have to provide individual serving certificates to each component. These customers needed an easy way to see all the routes that required customization along with a way to configure them.

A stock installation contains the following routes, which may need customization for both names and serving certificates/keys:

  • openshift-authentication oauth-openshift
  • openshift-console console
  • openshift-console downloads
  • openshift-monitoring alertmanager-main
  • openshift-monitoring grafana
  • openshift-monitoring prometheus-k8s
  • openshift-monitoring thanos-querier

How we responded: The team came up with a generic solution that provides a single point of configuration for Cluster Admins using a new CustomDomains API.

The console supported custom routes on the operator config prior to 4.8 (for the console route only). However, with the new CustomDomains API, we have introduced a unified way to stock install custom domains for routes that supports both names and serving certificates/keys.

For console and downloads routes, custom routes are now implemented to use the new ingress route configuration API.  

To customize the console route, log in to the cluster as a user with administrative privileges. Set the custom hostname and, if needed, set the TLS on the ingress config’s spec:

A secret is only required if the custom hostname suffix does not  match the cluster domain suffix.

To customize the the downloads route, set the custom hostname and, if needed, set the TLS on the ingress config’s spec:

Note: The console-operator config is in the process of being deprecated. If the console custom route is set up in both the ingress config and console-operator config, the new ingress config custom route will take precedence.

Distinguishing Between RunC and Kata Containers in the Console

What we heard: As deployments begin to use Kata container pods, customers need a mechanism to distinguish between runC and Kata container RuntimeClasses.

How we responded: We introduced Kata containers in tech preview for OpenShift 4.8.

Surfacing the RuntimeClass field in the Pod details page will help users identify which deployments are using Kata container pods. The RuntimeClass heading should have a popover description that can be pulled from the schema.

On the Pod details page, the RuntimeClass field label links to a popover displaying information on RuntimeClass from the schema.

Connect With Us

We are  always growing and evolving our improvements to OpenShift with a customer-first mindset. Be on the lookout for more enhancements in future releases. And do not  forget to complete our current Breadcrumbs usability activity or sign up to participate in future research endeavors to share your OpenShift experiences.  

Let us know your thoughts. We would  love to connect with users like you. Stay up to speed with the OpenShift design team on our OpenShift Design site, and be sure to catch us on the OpenShift Twitch channel.