We are supported by readers, when you click & purchase through links on our site we earn affiliate commission. Learn more.

Kong Mesh and Kuma reach new major versions

Following the familiar pattern, Kong announced new versions of Kuma and Kong Mesh at the same time. In addition to the open-service mesh Kuma 1.4, the Kong Mesh based on it is available in version 1.5. Kong Mesh is an additional Envoy-based service mesh that can be operated on Kubernetes and Virtual Machines (VM) in any cloud. The new version uses role-based access control (RBAC).

Role Based Access Control is activated by default in Kong Mesh 1.5 and can be used in different environments, clouds and in standalone and multi-zone deployments. The method is used to grant access to resources and actions only to certain users or groups based on their user roles.

Kong Mesh sets the concepts for this AccessRole to define a role as well AccessRoleBinding to assign a set of AccessRoles to a set of subjects – i.e. users and groups. Both concepts are global, that is, they are not tied to a mesh. In Kubernetes, users are identified by their from kubectl login provided log-in credentials. In Universal, the Kuma User Token is used for this.

The role-based access control is intended to lay the foundation for being able to add OpenID Connect (OIDC) and Lightweight Directory Access Protocol (LDAP) to authenticate users in Kong Mesh in the future.

The company behind Kuma, Kong, uses a new performance suite to help identify and fix possible performance problems in Kuma. With their help, Kuma 1.4 should use the underlying Postgres database in universal-Mode less overload.

These and other innovations can be found in a Kong blog entry. The changelogs for Kong Mesh 1.5 and for Kuma 1.4 offer further information.

(May)

To home page