Replicated Monthly Release Highlights - June 2026

What's New for Enterprise Portal

Enterprise Portal (New) is now the default for new Replicated teams. The next-generation Enterprise Portal, built on a GitHub-driven content model, launched in Alpha and is now the default experience for every new team on the platform. All portal content, including pages, navigation, and branding, is managed through a GitHub repo you control. Interactive MDX components adapt dynamically to each customer's license and instance state, git branches map automatically to versioned docs, and a local CLI preview lets you test changes with live reload before publishing. Auto-generated Helm chart reference docs and Terraform module distribution are built in. The new portal currently supports Embedded Cluster and Helm CLI install methods. Docs

Existing vendors interested in trying Enterprise Portal (New) can contact their account team to have it enabled. Once turned on, both versions run in parallel, and individual customers can be opted in independently, so you can test with a single customer before rolling out more broadly. New capabilities are continuing to land, and we're starting to look at how vendors currently using Classic can easily transition.

Support bundle uploads increased from 500 MB to 2 GB. Uploads in Enterprise Portal (New) now go directly to S3 for better performance and reliability. The Classic Enterprise Portal retains the 500 MB limit.

What's New for Vendor Portal

Event notifications is now generally available. After a successful beta period, event notifications are GA. Vendors can subscribe to events across instances, releases, and customers, and route alerts to email, webhooks, or Slack. Read the full announcement in the GA blog post. Alongside GA, several new capabilities have landed:

• CLI support for notification subscriptions. Vendors can now create, update, list, and delete notification subscriptions entirely from the Replicated CLI, closing the last manual gap in customer onboarding automation. Teams managing dozens or hundreds of customers can script bulk standardization, template configs in version control, and enforce consistency programmatically.

• Release build failed notification. A new notification event fires when a release build fails after promotion. Failed builds affect more than air gap bundles: Enterprise Portal docs, Download Portal release lists, install instructions, and Embedded Cluster installs can all be impacted. We recommend all vendors enable this under Notifications > New Notification in the Release category.

• Instance tag filtering. Vendors can now add tag-based filter conditions to 8 instance-scoped notification events, targeting alerts to specific instances based on tags like environment, region, or tier.

• Mute instance health alerts. Vendors can mute specific instances on a per-subscription basis for 7 days, 30 days, or indefinitely. Mutes are cluster-aware, so snapshot/restore scenarios with duplicate instance IDs won't accidentally silence alerts for the wrong cluster. Active mutes are visible from the notification History tab.

• Per-subscription webhook failure contact. When a webhook notification permanently fails after all retries, vendors can now choose exactly who gets notified. Set a per-subscription failure contact, either a team member or a free-form email address for routing to services like PagerDuty or OpsGenie, instead of alerting the subscription creator and every team admin.

What's New for Embedded Cluster

Embedded Cluster v3 beta continues to add major capabilities. Automated multi-node upgrades eliminate the per-node CLI commands previously required during cluster upgrades. Custom node roles let vendors define roles with associated labels applied at join time. Bring-your-own registry support lets customers pull images through their own internal registry during installation. Other additions include an external HTTP API for headless installations, TLS client certificate auth for custom registries, TLS certificate pinning on node-join commands, and application preflights that now also run during upgrades. Release notes

Kubernetes 1.35 support for Embedded Cluster v2. Version 2.18.1 adds support for Kubernetes 1.35 and removes support for Kubernetes 1.32. Vendors currently on Kubernetes 1.32 should upgrade to 1.33 or 1.34 before moving to 1.35, as Kubernetes does not support skipping minor versions. This release also adds nftables support for Linux kernel 6.17+. Release notes

Documentation Updates

New Concepts section for faster vendor onboarding. The Get Started section of the docs now includes a structured set of concept pages covering the platform's core building blocks: installation options, customer licensing, application delivery, the release lifecycle, telemetry and reporting, and support tooling. These pages are designed to help new vendors build a mental model of the platform before diving into implementation. Docs