.png)
Online KOTS and kURL install and upgrade instructions
When the Enterprise Portal added support for KOTS and kURL customers last month, it focused on air gap use cases. It now covers connected ones too. For customers who install and upgrade over the network, the portal generates the commands they need directly, the same way it already does for Helm and Embedded Cluster. Your KOTS and kURL customers get a consistent, self-serve path to their install and upgrade instructions instead of a separate process. You can read more in the Enterprise Portal documentation.
Able to automate KOTS and kURL through the headless API
The Enterprise Portal's headless API already let customers automate their installs with a service account token. That automation now includes KOTS and kURL. Customers who drive deployments through scripts or pipelines can create and manage those installs through the API rather than the portal UI, which fits the way many teams run their environments. See service account automation for how to set it up.
Customers are increasingly asked to prove that the software they run came from where it claims to. Two changes this month make that easier to answer for the tools and releases you distribute through Replicated.
Verify the Troubleshoot CLI binaries you download
The preflight and support-bundle CLIs now ship with signed SLSA provenance. When you or your customers download these tools, you can use Cosign to confirm that each archive came from the genuine Troubleshoot release pipeline and was not altered along the way. The provenance documentation walks through the verification steps.
Verify your Embedded Cluster v3 releases
Embedded Cluster v3 releases now include signed provenance and signatures for the release archive and the installer binary, along with a signed SBOM, beginning with version 3.14.0-beta.1. Before running an installer, you or your customers can verify with Cosign that it came from Replicated. The release verification documentation covers each file and command.
Reserve an additional slug alias for your application
Renaming an application as part of a rebranding effort can risk breaking the install references your customers already rely on. Vendors can now reserve a slug alias, a second permanent slug that keeps resolving alongside your primary one, so introducing a new customer-facing name does not invalidate the commands and URLs already in the field. The slug alias documentation covers any current limitations. The new capability is available on the Enterprise plan, so reach out if you would like to learn more.
Disaster recovery in Embedded Cluster v3 available in alpha
Disaster recovery for Embedded Cluster v3 has been coming together over the past several weeks, including backup and restore for air gap environments. It is still early, and we are working with teams hands-on as it matures. If disaster recovery on Embedded Cluster v3 is something you need, reach out and we will help you try it. For the rest of what is shipping in v3 on its way to general availability, the release notes have the details.