Merge branch 'main' into 120396

Author: paigecalvert

.github/dependabot.yml

@@ -5,9 +5,18 @@ updates:
     directory: "/" # Root directory
     schedule:
       interval: "weekly"
+    open-pull-requests-limit: 10
+    labels:
+      - "dependencies"
+      - "npm"
+      - "type::security"
 
   # Keep Dependabot itself up to date
   - package-ecosystem: "github-actions"
     directory: "/" # Root directory (or specify if actions are elsewhere)
     schedule:
       interval: "weekly"
+    labels:
+      - "dependencies"
+      - "github-actions"
+      - "type::security"

README.md

@@ -40,39 +40,52 @@ This repository has been made public so that vendors and the open-source communi
 
 This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
 
-When you submit a PR in GitHub, Netlify builds a preview automatically. However, you can preview your changes locally. To do this, you must install `yarn` and run a build to create a Docusaurus preview in your local browser.
+When you submit a PR in GitHub, Netlify builds a preview automatically. However, you can preview your changes locally using Node.js and npm. This repository uses npm as its package manager.
 
-### Install yarn
+### Prerequisites
 
-The Yarn documentation recommends installing Yarn using the npm package manager, which comes bundled with Node.js when you install it on your system.
+- Node.js version 18 or higher
+- npm (comes bundled with Node.js)
 
-After you install npm, you can run the following both to install and upgrade Yarn:
+### Start the local dev server with `npm start`
 
-```
-npm install --global yarn
-```
+1. Install dependencies using npm:
+
+  ```bash
+  npm install
+  ```
 
-If you use Homebrew, you can run this command to install Yarn:
+2. Start a local development server in a browser window:
 
-```
-$ brew install yarn
-```
+  ```bash
+  npm start
+  ```
 
-### Create a Local Development Server and WYSIWYG Preview
+Most changes are reflected live without having to restart the server (changes to the sidebar file typically require restarting the dev server). This preview shows the formatting and styles as they would render on the live site.
 
-1. Install the docusaurus package using Yarn:
+If you encounter any build errors, they will appear in the terminal and often indicate issues like broken links or formatting problems in the content.
 
-  ```
-  yarn add docusaurus
-  ```
+## Build and test locally with `npm run build` and `npm run serve`
 
-1. Run the following command to start a local development server and open up a browser window. Most changes are reflected live without having to restart the server. This preview shows the formatting and styles as they would render on the live site (also known as what-you-see-is-what-you-get or WYSIWYG), which can be more helpful than viewing content in a VS Code preview.
+Before pushing changes to the remote repository, build and serve the site locally to check for errors, including broken links.
 
-  ```
-  $ yarn start
-  ```
+1. Install dependencies using npm:
 
-  If `yarn start` refuses to start, try reinstalling the `yarn` CLI. You do not need to uninstall `yarn` before reinstalling it. However, if you get build errors from your content, such as broken links, the Preview itself fails and error messages appear in the terminal that can help you troubleshoot the problems in the content.
+  ```bash
+  npm install
+  ```
+1. Build the static site files:
+   
+   ```bash
+   npm run build
+   ```
+   Any broken links and anchor links are listed in the output.
+
+1. Serve the `build` directory locally to test:
+
+   ```bash
+   npm run serve
+   ```
 
 ## Folder Structure and TOC
 

docs/enterprise/installing-embedded-automation.mdx

@@ -1,15 +1,15 @@
 import ConfigValuesExample from "../partials/configValues/_configValuesExample.mdx"
 import ConfigValuesProcedure from "../partials/configValues/_config-values-procedure.mdx"
 
-# Installing with Embedded Cluster from the Command Line
+# Automating Installation with Embedded Cluster
 
-This topic describes how to install an application with Replicated Embedded Cluster from the command line.
+This topic describes how to install an application with Replicated Embedded Cluster from the command line, without needing to access the Replicated KOTS Admin Console.
 
 ## Overview
 
-You can use the command line to install an application with Replicated Embedded Cluster. A common use case for installing from the command line is to automate installation, such as performing headless installations as part of CI/CD pipelines.
+A common use case for installing with Embedded Cluster from the command line is to automate installation, such as performing headless installations as part of CI/CD pipelines.
 
-To install from the command line, you provide all the necessary installation assets, such as the license file and the application config values, with the installation command rather than through the Admin Console UI. Any preflight checks defined for the application run automatically during headless installations from the command line rather than being displayed in the Admin Console.
+With headless installation, you provide all the necessary installation assets, such as the license file and the application config values, with the installation command rather than through the Admin Console UI. Any preflight checks defined for the application run automatically during headless installations from the command line rather than being displayed in the Admin Console.
 
 ## Prerequisite
 

docs/enterprise/installing-embedded-requirements.mdx

@@ -38,3 +38,52 @@ This topic lists the installation requirements for Replicated Embedded Cluster.
 </table>
 
 &#42; Required only if the application uses the [Replicated private registry](/vendor/private-images-replicated).
+
+## About Firewalld Configuration
+
+When Firewalld is enabled in the installation environment, Embedded Cluster modifies the Firewalld config to allow traffic over the pod and service networks and to open the required ports on the host. No additional configuration is required.
+
+The following rule is added to Firewalld:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<zone target="ACCEPT">
+  <interface name="cali+"/>
+  <interface name="tunl+"/>
+  <interface name="vxlan-v6.calico"/>
+  <interface name="vxlan.calico"/>
+  <interface name="wg-v6.cali"/>
+  <interface name="wireguard.cali"/>
+  <source address="[pod-network-cidr]"/>
+  <source address="[service-network-cidr]"/>
+</zone>
+```
+
+The following ports are opened in the default zone:
+
+<table>
+<tr>
+  <th>Port</th>
+  <th>Protocol</th>
+</tr>
+<tr>
+  <td>6443</td>
+  <td>TCP</td>
+</tr>
+<tr>
+  <td>10250</td>
+  <td>TCP</td>
+</tr>
+<tr>
+  <td>9443</td>
+  <td>TCP</td>
+</tr>
+<tr>
+  <td>2380</td>
+  <td>TCP</td>
+</tr>
+<tr>
+  <td>4789</td>
+  <td>UDP</td>
+</tr>
+</table>

docs/partials/embedded-cluster/_ec-config.mdx

@@ -2,5 +2,5 @@
 apiVersion: embeddedcluster.replicated.com/v1beta1
 kind: Config
 spec:
-  version: 1.21.0+k8s-1.30
+  version: 2.1.3+k8s-1.30
 ```

docs/partials/embedded-cluster/_port-reqs.mdx

@@ -36,8 +36,8 @@ Additionally, port 30000 must be accessible by nodes joining the cluster.
 
 If port 30000 is occupied, you can select a different port for the Admin Console during installation. For more information, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).
 
-#### LAM Port (Air Gap Only)
+#### LAM Port
 
-In addition to the ports above, air gap installations also require that port 50000/TCP is open and available for the Local Artifact Mirror (LAM).
+The Local Artifact Mirror (LAM) requires that port 50000/TCP is open and available.
 
 If port 50000 is occupied, you can select a different port for the LAM during installation. For more information, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).

docs/partials/getting-started/_gitea-ec-config.mdx

@@ -2,5 +2,5 @@
 apiVersion: embeddedcluster.replicated.com/v1beta1
 kind: Config
 spec:
-  version: 1.21.0+k8s-1.30
+  version: 2.1.3+k8s-1.30
 ```

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

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

docs/reference/embedded-cluster-install.mdx

@@ -48,7 +48,7 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
   <tr>
      <td>`--config-values`</td>
      <td>
-        <p>Path to the ConfigValues file for the application. The ConfigValues file can be used to pass the application configuration values from the command line during installation, such as when performing automated installations as part of CI/CD pipelines. For more information, see [Installing with Embedded Cluster from the Command Line](/enterprise/installing-embedded-automation).</p>
+        <p>Path to the ConfigValues file for the application. The ConfigValues file can be used to pass the application configuration values from the command line during installation, such as when performing automated installations as part of CI/CD pipelines. For more information, see [Automating Installation with Embedded Cluster](/enterprise/installing-embedded-automation).</p>
         <p><strong>Requirement:</strong> Embedded Cluster 1.18.0 and later.</p>
      </td>
   </tr>

docs/reference/embedded-config.mdx

@@ -24,7 +24,7 @@ For additional property-specific limitations, see the sections below.
 apiVersion: embeddedcluster.replicated.com/v1beta1
 kind: Config
 spec:
-  version: 1.21.0+k8s-1.30
+  version: 2.1.3+k8s-1.30
   roles:
     controller:
       name: management