Service Mesh 1.1 released

Service Mesh OpenShift

- Thomas Jungbauer Thomas Jungbauer ( Lastmod: 2024-05-05 ) - 1 min read

April 10th 2020 Red Hat released Service Mesh version 1.1 which supports the following versions:

  • Istio - 1.4.6

  • Kiali - 1.12.7

  • Jaeger - 1.17.1

Update

To update an operator like Service Mesh, the Operator Life Cycle Manager takes care and automatically updates everything (unless it was configured differently).

For the Service Mesh 1.1 update consult Upgrading Red Hat OpenShift Service Mesh
It is important to add the version number to the ServiceMeshControlPlane object. The easiest way to do so is:

  • Log into OpenShift

  • Select the Namespace istio-system

  • Goto _"Installed Operators > Red Hat OpenShift Service Mesh > ServiceMeshControlPlanes > basic-install > YAML"

  • Under spec add the following:

    spec:
  version: v1.1

Notable Changes

ServiceMeshMember Object

With the ServiceMeshMember object it is now possible that a project administrator can add a service to the service mesh, instead relying on the cluster administrator to configure the ServiceMeshMemberRoll. To do so create the following object (i.e. under the namespace tutorial)

apiVersion: maistra.io/v1
kind: ServiceMeshMember
metadata:
  name: default
  namespace: tutorial
spec:
  controlPlaneRef:
    name: basic-install (1)
    namespace: istio-system (2)
1Name of the ServiceMeshControlPlane object
2name of the service mesh namespace

See Also:

  • What's new in OpenShift, 4.20 Edition –

    This article covers news and updates in the OpenShift 4.20 release. We focus on points that got our attention, but this is not a complete summary of the release notes.

  • Red Hat Quay Registry - Integrate Keycloak –

    This guide shows you how to configure Keycloak as an OpenID Connect (OIDC) provider for Red Hat Quay Registry. It covers what to configure in Keycloak, what to put into Quay’s config.yaml (or Operator config), how to verify the login flow, and how to switch your Quay initial/admin account (stored locally in Quay’s DB) to an admin user that authenticates via Keycloak.

  • A second look into the Kubernetes Gateway API on OpenShift –

    This is our second look into the Kubernetes Gateway API an it’s integration into OpenShift. This post covers TLS configuration. The Kubernetes Gateway API is new implementation of the ingress, load balancing and service mesh API’s. See upstream for more information. Also the OpenShift documentation provides an overview of the Gateway API and it’s integration. We demonstrate how to add TLS to our Nginx deployment, how to implement a shared Gateway and finally how to implement HTTP to HTTPS redirection with the Gateway API. Furthermore we cover how HTTPRoute objects attach to Gateways and dive into ordering of HTTPRoute objects.

  • A first look into the Kubernetes Gateway API on OpenShift –

    This blog post summarizes our first look into the Kubernetes Gateway API and how it is integrated in OpenShift.

  • Reusable Argo CD Application Helm Template –

    When working with Argo CD at scale, you often find yourself creating similar Application manifests repeatedly. Each application needs the same basic structure but with different configurations for source repositories, destinations, and sync policies. Additionally, managing namespace metadata becomes tricky when you need to conditionally control whether Argo CD should manage namespace metadata based on sync options. In this article, I’ll walk you through a reusable Helm template that solves these challenges by providing a flexible, DRY (Don’t Repeat Yourself) approach to creating Argo CD Applications. This template is available in my public Helm Chart library and can easily be used by anyone.

Copyright © 2020 - 2025 Toni Schmidbauer & Thomas Jungbauer