Known Issues

In some cases, the meshPanel displays outdated state after navigating between views without a full page reload. Two known symptoms: False "no payment method assigned" warning — The panel keeps showing a payment method warning even though a payment method has already been assigned. False "You are not a member of this project" error — After navigating to a project the user is a member of, a membership error is incorrectly displayed. Workaround: Performing a full page reload resolves the issue in both cases. We are tracking this as a state management improvement to ensure the UI correctly refreshes its state after navigation, without requiring a manual reload.

Who is affected Only customers using Terraform <= 1.5.5 (not OpenTofu) are affected. This is caused by an expired PGP signing key used to verify Terraform binary checksums during installation. Root cause This is a known upstream bug in HashiCorp's hc-install tool, which meshStack uses internally to download and verify Terraform binaries. The issue is present since 18.04.2026. The issue has been reported to HashiCorp: https://github.com/hashicorp/hc-install/issues/370 Workaround / Fix We are currently investigating a workaround on our end. Using OpenTofu instead of Terraform would solve the issue, but we are currently checking the consequences of this migration for existing Building Blocks. Status: Under investigation — no fix available from HashiCorp yet.

We are currently observing elevated error rates affecting managed meshStack instances in our SaaS service. meshStack SaaS is hosted on Google Cloud Platform (GCP) on GKE. This behavior is primarily linked to a surge in infrastructure maintenance events in GKE. Technical Details Our engineering team has identified two primary external factors contributing to this instability: CVE-2026-23268 (CrackArmor) Patching : Google is currently rolling out kernel-level mitigations for "CrackArmor" vulnerabilities. This has resulted in an increased frequency of node reboots and live migrations. On our current N2 nodes we see long provisioning times for new nodes to replace failed hosts. While our service is designed to withstand these maintenance events, customers may observe intermittent errors. Since this is the second time node migrations have impacted our service, we are looking at long term solutions Affected Components All meshStack SaaS services (meshPanel, meshStack API) Customers hosted on our GCP-based SaaS infrastructure Status and Next Steps To stabilize the environment and reduce the impact of these maintenance events, we are taking the following actions: Node Type Migration: We are accelerating a migration of affected workloads from N2 instances to more modern instance types. This move is designed to provide better stability during maintenance and decouple our infrastructure from any hardware-specific issues seen on the N2 family. Review of node pool sizing: we are allocating more headroom for maintenance events Timeline We will provide the next update on our instance migration process by April 24th.

I created a new draft version for a parent Building Block Definition and added a new output to it. When I go to the child and it is also a draft, I would expect to be able to pick this new output, as I want to develop both definitions in parallel as the new child version relies on the new parent output. But I only see the outputs of the released version. The workaround to this issue is, to first release the new version of the parent definition, which should be a feasible approach in most cases. But it would improve the experience for a Building Block Definition developer, if he could first test both definitions with the new dependency in its own workspace before releasing them in the new version. If the parent definition is draft in v1, it just works fine and I can pick all outputs. But when it was already released before and I just create a new draft version of it, it does not work as I expected it to work.

Detailed tenant usage reports, which are available for OpenShift, OpenStack, Cloud Foundry, and OSB Services, provide additional insights into usage data. However, even when currency conversion is enabled, these reports continue to display the original currency from the provider instead of the converted currency. Thanks for your understanding while we are working to solve this issue

We recently had the case that our Entra deleted users by accident and this triggered the deactivation of users in meshStack. Entra team created new users, the new users got new object ids. After 30 days, Entra sent a delete command to meshStack for the users with the old object ids. This triggered a deletion of users in meshStack. Expected: meshStack SCIM sync differentiates users by object id, not by username.

Description: When a user is assigned multiple roles within the same workspace (e.g., both Workspace Owner and Workspace Manager), they receive duplicate email notifications related to communications, role expiration, and similar events. This occurs because the system treats each role independently for notification purposes. Impact: Affected users may experience confusion or cluttered inboxes due to receiving multiple copies of the same email notification. Workaround: To avoid duplicate notifications, assign only the highest applicable role to the user within the workspace.

Description: When a tenant (e.g., a GCP project) incurs no cost—either due to inactivity or because all usage is covered by free consumption credits—the tenant is no longer displayed in the Unmanaged Tenant List. Additionally, Tenant Usage Reports are not generated or shown in such cases. Impact: This behavior reduces transparency, as it prevents users from tracking resource consumption even when costs are offset by credits. As a result, tenants utilizing free credits may appear inactive or unaccounted for in reporting and monitoring views. Expected Behavior: Even if no charges are incurred, tenants should remain visible in the Unmanaged Tenant List and Tenant Usage Reports should reflect credit-based consumption. This would ensure full visibility into resource usage and promote better tracking and accountability.

As a admin user of meshStack I would like to make sure I am creating the payment method for the correct workspace by seeing the workspace identifier. At the moment only the display name of a workspace is shown and names are not unique inside meshStack.

At the moment the CSV Export from meshStack is using the US style number format. This means that Thousands separator using , and decimal separator . It would be great to either have a dynamic decision based on the settings of the OS / Web Browser location. Or having the option to select which number format to download.