Merge branch 'main' into EP-GA-update

Author: paigecalvert

.github/workflows/app-manager-release-notes.yml

@@ -22,7 +22,7 @@ jobs:
         owner-repo: replicatedhq/kots
         head: $KOTS_VERSION
         title: ${KOTS_VERSION#v}
-        description: 'Support for Kubernetes: 1.31, 1.32, and 1.33'
+        description: 'Support for Kubernetes: 1.31, 1.32, 1.33, and 1.34'
         include-pr-links: false
         github-token: ${{ secrets.GITHUB_TOKEN }}
 

docs/enterprise/installing-general-requirements.mdx

@@ -266,7 +266,9 @@ KOTS has been tested for compatibility with the following registries:
 
 <DockerCompatibility/>
 
-## Firewall Openings for Online Installations with KOTS in an Existing Cluster {#firewall}
+## Network Requirements for Online Installations
+
+### Firewall Openings {#firewall}
 
 <FirewallOpeningsIntro/>
 
@@ -304,3 +306,7 @@ KOTS has been tested for compatibility with the following registries:
 &#42; Required only if the application uses the [Replicated proxy registry](/vendor/private-images-about).
 
 &#42;&#42; Required only if the application uses the [Replicated registry](/vendor/private-images-replicated).
+
+### IPv4 or IPv4/IPv6 Dual-Stack Only
+
+KOTS does not support online installations in single-stack IPv6-only environments. Environments that use IPv4 or dual-stack IPv4/IPv6 networking are supported.

docs/enterprise/installing-kurl-requirements.mdx

@@ -36,7 +36,9 @@ You must meet the additional kURL system requirements when applicable:
 
 - **Cloud Disk Performance**: For a list of cloud VM instance and disk combinations that are known to provide sufficient performance for etcd and pass the write latency preflight, see [Cloud Disk Performance](https://kurl.sh/docs/install-with-kurl/system-requirements#cloud-disk-performance) in the kURL documentation.
 
-## Firewall Openings for Online Installations with kURL {#firewall}
+## Network Requirements for Online Installations
+
+### Firewall Openings {#firewall}
 
 <FirewallOpeningsIntro/>
 
@@ -73,4 +75,8 @@ You must meet the additional kURL system requirements when applicable:
 
 &#42; Required only if the application uses the [Replicated proxy registry](/vendor/private-images-about).
 
-&#42;&#42; Required only if the application uses the [Replicated registry](/vendor/private-images-replicated).
+&#42;&#42; Required only if the application uses the [Replicated registry](/vendor/private-images-replicated).
+
+### IPv4 or IPv4/IPv6 Dual-Stack Only
+
+kURL does not support online installations in single-stack IPv6-only environments. Environments that use IPv4 or dual-stack IPv4/IPv6 networking are supported.

docs/intro-replicated.mdx

@@ -27,7 +27,7 @@ The following diagram demonstrates the process of using the Replicated Platform
 
 [View a larger version of this image](/images/replicated-platform.png)
 
-The diagram above shows an application that is packaged with the [**Replicated SDK**](/vendor/replicated-sdk-overview). The application is tested in clusters provisioned with the [**Replicated Compatibility Matrix**](/vendor/testing-about), then added to a new release in the [**Vendor Portal**](/vendor/releases-about) using an automated CI/CD pipeline.
+The diagram above shows an application that is packaged with the [**Replicated SDK**](/vendor/replicated-sdk-overview). The application is tested in clusters provisioned with the [**Replicated Compatibility Matrix (CMX)**](/vendor/testing-about), then added to a new release in the [**Vendor Portal**](/vendor/releases-about) using an automated CI/CD pipeline.
 
 The application is then installed by a customer ("Big Bank") on a VM. To install, the customer downloads their license, which grants proxy access to the application images through the [**Replicated proxy registry**](/vendor/private-images-about). They also download the installation assets for the [**Replicated Embedded Cluster**](/vendor/embedded-overview) installer.
 
@@ -101,11 +101,11 @@ The following shows an example of the Enterprise Portal dashboard:
 
 ### Compatibility Matrix
 
-Replicated Compatibility Matrix can be used to create VMs or Kubernetes clusters within minutes or less. You can interact with Compatibility Matrix through the Vendor Portal or the Replicated CLI, making it possible to integrate Compatibility Matrix into your existing CI/CD workflows to programmatically create test environments.
+Replicated Compatibility Matrix (CMX) can be used to create VMs or Kubernetes clusters within minutes or less. You can interact with CMX through the Vendor Portal or the Replicated CLI, making it possible to integrate CMX into your existing CI/CD workflows to programmatically create test environments.
 
-For more information, see [About Compatibility Matrix](/vendor/testing-about).
+For more information, see [About CMX](/vendor/testing-about).
 
-The following shows the Compatibility Matrix page for creating a cluster:
+The following shows the CMX page for creating a cluster:
 
 <img alt="Create a cluster page" src="/images/create-a-cluster.png" width="650px"/>
 
@@ -143,9 +143,9 @@ For more information about using the Replicated SDK, see [About the Replicated S
 
 ### Test
 
-The Compatibility Matrix can be used to quickly provision ephemeral VMs and Kubernetes clusters. When integrated into existing CI/CD workflows, the Compatibility Matrix can be used to automatically create a variety of customer-representative environments for testing code changes.
+The CMX can be used to quickly provision ephemeral VMs and Kubernetes clusters. When integrated into existing CI/CD workflows, the CMX can be used to automatically create a variety of customer-representative environments for testing code changes.
 
-For more information, see [About Compatibility Matrix](/vendor/testing-about).
+For more information, see [About CMX](/vendor/testing-about).
 
 ### License
 
@@ -186,5 +186,5 @@ ISVs can also set up email and Slack notifications to get alerted of important i
 Support teams can use Replicated features to more quickly diagnose and resolve application issues. For example:
 
 - Customize and generate support bundles, which collect and analyze redacted information from the customer's cluster, environment, and application instance. See [About Preflight Checks and Support Bundles](/vendor/preflight-support-bundle-about).
-- Provision customer-representative environments with Compatibility Matrix to recreate and diagnose issues. See [About Compatibility Matrix](/vendor/testing-about).
+- Provision customer-representative environments with CMX to recreate and diagnose issues. See [About CMX](/vendor/testing-about).
 - Get insights into an instance's status by accessing telemetry data, which covers the health of the application, the current application version, and details about the infrastructure and cluster where the application is running. For more information, see [Customer Reporting](/vendor/customer-reporting). For more information, see [Customer Reporting](/vendor/customer-reporting).

docs/partials/ci-cd/_test-recs.mdx

@@ -1,9 +1,9 @@
-* **Application Testing:** Traditional application testing includes unit, integration, and end-to-end tests. These tests are critical for application reliability, and Compatibility Matrix is designed to to incorporate and use your application testing.
+* **Application Testing:** Traditional application testing includes unit, integration, and end-to-end tests. These tests are critical for application reliability, and CMX is designed to to incorporate and use your application testing.
 
 * **Performance Testing:** Performance testing is used to benchmark your application to ensure it can handle the expected load and scale gracefully. Test your application under a range of workloads and scenarios to identify any bottlenecks or performance issues. Make sure to optimize your application for different Kubernetes distributions and configurations by creating all of the environments you need to test in.
 
 * **Smoke Testing:** Using a single, conformant Kubernetes distribution to test basic functionality of your application with default (or standard) configuration values is a quick way to get feedback if something is likely to be broken for all or most customers. Replicated also recommends that you include each Kubernetes version that you intend to support in your smoke tests.
 
-* **Compatibility Testing:** Because applications run on various Kubernetes distributions and configurations, it is important to test compatibility across different environments. Compatibility Matrix provides this infrastructure.
+* **Compatibility Testing:** Because applications run on various Kubernetes distributions and configurations, it is important to test compatibility across different environments. CMX provides this infrastructure.
 
-* **Canary Testing:** Before releasing to all customers, consider deploying your application to a small subset of your customer base as a _canary_ release. This lets you monitor the application's performance and stability in real-world environments, while minimizing the impact of potential issues. Compatibility Matrix enables canary testing by simulating exact (or near) customer environments and configurations to test your application with.
+* **Canary Testing:** Before releasing to all customers, consider deploying your application to a small subset of your customer base as a _canary_ release. This lets you monitor the application's performance and stability in real-world environments, while minimizing the impact of potential issues. CMX enables canary testing by simulating exact (or near) customer environments and configurations to test your application with.

docs/partials/install/_kubernetes-compatibility.mdx

@@ -1,5 +1,6 @@
 | KOTS Versions          | Kubernetes Compatibility    |
 |------------------------|-----------------------------|
-| 1.124.17 and later     | 1.33, 1.32, 1.31            | 
-| 1.123.0 and later      | 1.32, 1.31                  |
+| 1.128.3 and later      | 1.34, 1.33, 1.32, 1.31      | 
+| 1.124.17 to 1.128.3    | 1.33, 1.32, 1.31            | 
+| 1.123.0 to 1.124.16    | 1.32, 1.31                  |
 | 1.117.0 to 1.122.1     | 1.31                        |

docs/partials/replicated-sdk/_dependency-yaml.mdx

@@ -3,7 +3,7 @@
 dependencies:
 - name: replicated
   repository: oci://registry.replicated.com/library
-  version: 1.9.0
+  version: 1.11.0
 ```
 
 For the latest version information for the Replicated SDK, see the [replicated-sdk repository](https://github.com/replicatedhq/replicated-sdk/releases) in GitHub.

docs/release-notes/rn-app-manager.md

@@ -18,6 +18,20 @@ The following table lists the versions of Kubernetes that are compatible with ea
 
 <!--RELEASE_NOTES_PLACEHOLDER-->
 
+## 1.128.3
+
+Released on October 28, 2025
+
+Support for Kubernetes: 1.31, 1.32, 1.33, and 1.34
+
+### Improvements {#improvements-1-128-3}
+* Adds fully qualified registry prefix for KOTS to improve registry handling.
+* Updates multiple security dependencies to address potential vulnerabilities.
+
+### Bug Fixes {#bug-fixes-1-128-3}
+* Fixes an issue when editing the release config on Embedded Cluster where the sidebar items would disappear.
+* Fixes an issue where channel switches in Embedded Cluster installations would skip infrastructure upgrades, leaving the cluster on an outdated Kubernetes version.
+
 ## 1.128.2
 
 Released on September 29, 2025

docs/release-notes/rn-embedded-cluster.md

@@ -12,6 +12,34 @@ Additionally, these release notes list the versions of Kubernetes and Replicated
 
 <!--RELEASE_NOTES_PLACEHOLDER-->
 
+## 2.12.0
+
+Released on October 30, 2025
+
+<table>
+  <tr>
+    <th>Version</th>
+    <td id="center">2.12.0+k8s-1.33</td>
+    <td id="center">2.12.0+k8s-1.32</td>
+    <td id="center">2.12.0+k8s-1.31</td>
+  </tr>
+  <tr>
+    <th>Kubernetes Version</th>
+    <td id="center">1.33.4</td>
+    <td id="center">1.32.8</td>
+    <td id="center">1.31.12</td>
+  </tr>
+  <tr>
+    <th>KOTS Version</th>
+    <td colspan="3" id="center">1.128.3</td>
+  </tr>
+</table>
+
+### Bug Fixes {#bug-fixes-2-12-0}
+
+* Fixes instability in the highly available registry used for HA air gap installations, which was caused by flakiness in SeaweedFS Raft.
+* Fixes an issue where multi-document YAML files were not parsed correctly, which led to resources not being recognized in the release.
+
 ## 2.11.3
 
 Released on October 1, 2025

docs/release-notes/rn-replicated-sdk.md

@@ -8,6 +8,22 @@ pagination_prev: null
 
 This topic contains release notes for the [Replicated SDK](/vendor/replicated-sdk-overview). The release notes list new features, improvements, bug fixes, known issues, and breaking changes. 
 
+## 1.11.0
+
+Released on November 5, 2025
+
+### Improvements {#improvements-1-11-0}
+* Adds support for configuring image pull secrets with [`values.global.imagePullSecrets`](https://github.com/replicatedhq/replicated-sdk/blob/1.11.0/chart/values.yaml#L8) as well as the existing [`values.replicated.imagePullSecrets`](https://github.com/replicatedhq/replicated-sdk/blob/1.11.0/chart/values.yaml#L167).
+* Adds an image pull secret, titled `enterprise-pull-secret`.
+
+## 1.10.0
+
+Released on October 29, 2025
+
+### Improvements {#improvements-1-10-0}
+* Adds support for configuring a proxy for the SDK with [`proxy`](https://github.com/replicatedhq/replicated-sdk/blob/1.10.0/chart/values.yaml#L315). For more information, see [Proxy Configuration](/vendor/replicated-sdk-customizing#proxy).
+* Enables the use of `kots.io/v1beta2` licenses.
+
 ## 1.9.0
 
 Released on October 16, 2025