Replicated Monthly Release Highlights - April 2025

Paige Calvert
 | 
Apr 2, 2025

What’s New for Compatibility Matrix

Network ID is now visible as part of the [.inline] cluster ls [.inline] command. To make it easier for vendors to discover the network ID of a cluster without running multiple commands, a new “Network” column is added to the [.inline] cluster ls [.inline] Replicated CLI command.

Added autocomplete to the Replicated CLI [.inline]--distribution[.inline], [.inline]--version[.inline], and [.inline]--instance-type[.inline] flags. This improvement makes it easier to quickly spin up clusters with Compatibility Matrix from the command line. 

What’s New for Embedded Cluster

Added full support for custom domains (Embedded Cluster 2.2.0). Vendors can now add [.inline]spec.domains.replicatedAppDomain[.inline] and [.inline]spec.domains.proxyRegistryDomain[.inline] to their Embedded Cluster Config to alias the [.inline]replicated.app[.inline] and [.inline]proxy.replicated.com[.inline] endpoints with their custom domains. Docs.

Removed all calls to endpoints other than [.inline]replicated.app[.inline] and [.inline]proxy.replicated.com[.inline] (Embedded Cluster 2.2.0). Embedded Cluster no longer makes any calls to endpoints other than [.inline]replicated.app[.inline] and [.inline]proxy.replicated.com[.inline]. With this change, enterprises only need to whitelist two domains to install successfully with Embedded Cluster.

Improvements to the [.inline]join[.inline] command (Embedded Cluster 2.2.0). The [.inline]join[.inline] command now prints a warning message to the user that they should not join another node while a controller is being joined. Controller nodes should not be joined in parallel with other nodes because there can be race conditions, particularly when high availability is not yet enabled for the cluster. The [.inline]join[.inline] command also now waits until nodes in the cluster are ready before saying the join succeeded. 

Firewalld automatically configured during install (Embedded Cluster 2.1.2). To improve the installation experience for users installing in environments where firewalld is enabled, Embedded Cluster now automatically applies some firewalld rules during install.

New preflights checks. Various new preflight checks were added to help improve the installation success rate for Embedded Cluster users, including checks to ensure that the data directory is executable (2.2.0), that the data directory has the correct permissions (2.1.3), and that inotify kernel parameters were set (2.1.3).

What’s New for the Replicated SDK

Support for aliasing the [.inline]replicated.app[.inline] endpoint with a custom domain. The Replicated SDK now includes a [.inline]replicatedAppDomain[.inline] Helm value that vendors can set so that the SDK uses their custom domain. For more information, see values.yaml.tmpl in the replicated-sdk repository in GitHub.

What’s New for Product Documentation

Embedded Cluster architecture diagrams. New architecture diagrams in the Embedded Cluster Overview topic show how the different components are deployed in single-node, multi-node, and high availability Embedded Cluster installations. Docs.

Added descriptions of the Embedded Cluster built-in extensions. The docs now include detailed descriptions of each of the built-in extensions deployed by Embedded Cluster. Docs.

Added Embedded Custer troubleshooting information. A new page includes guidance for troubleshooting Embedded Cluster installations, including how to view logs, workarounds for common errors, and how to collect support bundles. Docs.

Documented the migration paths to the HelmChart v2 installation method. Vendors that need to migrate existing customers to the HelmChart v2 installation method can now reference the Migrating Existing Installations to HelmChart v2 page for information about the different supported migration paths. Docs.

New blog on how to choose between distributed storage or app-level data replication. This blog highlights the main decision points and trade-offs that ISVs need to consider when deciding how to handle data replication for customer-managed deployments of their app. Read more.