End of Sale Notice:

Commercial support for NGINX Service Mesh is available to customers who currently have active NGINX Microservices Bundle subscriptions. F5 NGINX announced the End of Sale (EoS) for the NGINX Microservices Bundles as of July 1, 2023.

See our End of Sale announcement for more details.

Release Notes 0.5.0

Release information for NGINX Service Mesh, a configurable, low‑latency infrastructure layer designed to handle a high volume of network‑based interprocess communication among application infrastructure services using application programming interfaces (APIs). Lists of new features and known issues are provided.

NGINX Service Mesh Version 0.5.0

These release notes provide general information and describe known issues for NGINX Service Mesh version 0.5.0, in the following categories:


NGINX Service Mesh 0.5.0 includes the following updates:

  • Support for stand-alone (kubeadm) clusters, including VSphere VM clusters.

  • Auto-detection of Persistent Volumes (PVs) for SPIRE.

  • Image names streamlined (affects deployment scripts).

  • Support for non-production environments without persistent volume (not recommended outside of testing)

Resolved Issues

This release includes fixes for the following issues.

  • NGINX Service Mesh may exit during network outages (13295)

  • Inject does not fully support multiple resources in a single JSON file (13531)

  • NGINX Service Mesh annotations are validated inconsistently (13927)

  • On using untested mesh tools or environments (15126)

  • Running nginx-meshctl returns the error “unable to get mesh config” (15416)

Known Issues

The following issues are known to be present in this release. Look for updates to these issues in future NGINX Service Mesh release notes.

NGINX Service Mesh may drop metrics (12282):
Prometheus and Service Mesh Interface (SMI) metrics may fail to return metrics values in rare cases.


If you notice that metrics aren’t returned, you should retry the request as the system will self-recover.