Merge branch 'main' into 106919

Author: paigecalvert

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

@@ -56,11 +56,9 @@ jobs:
 
     - name: Slack Notification
       uses: slackapi/[email protected]
-      with: 
+      with:
+        webhook: ${{ secrets.KOTS_RELEASE_NOTES_SLACK_WEBHOOK }}
+        webhook-type: webhook-trigger
         payload: |
-          {
-            "version": "${{ github.event.client_payload.version }}",
-            "pull_request_url": "${{steps.cpr.outputs.pull-request-url}}"
-          }
-      env:
-        SLACK_WEBHOOK_URL: ${{ secrets.KOTS_RELEASE_NOTES_SLACK_WEBHOOK }}
+          version: "${{ github.event.client_payload.version }}"
+          pull_request_url: "${{steps.cpr.outputs.pull-request-url}}"

.github/workflows/kubernetes-installer-release-notes.yml

@@ -56,11 +56,9 @@ jobs:
 
     - name: Slack Notification
       uses: slackapi/[email protected]
-      with: 
+      with:
+        webhook: ${{ secrets.KURL_RELEASE_NOTES_SLACK_WEBHOOK }}
+        webhook-type: webhook-trigger
         payload: |
-          {
-            "version": "${{ github.event.client_payload.version }}",
-            "pull_request_url": "${{steps.cpr.outputs.pull-request-url}}"
-          }
-      env:
-        SLACK_WEBHOOK_URL: ${{ secrets.KURL_RELEASE_NOTES_SLACK_WEBHOOK }}
+          version: "${{ github.event.client_payload.version }}"
+          pull_request_url: "${{steps.cpr.outputs.pull-request-url}}"

.github/workflows/replicated-sdk-release-notes.yml

@@ -60,11 +60,9 @@ jobs:
 
     - name: Slack Notification
       uses: slackapi/[email protected]
-      with: 
+      with:
+        webhook: ${{ secrets.REPLICATED_SDK_RELEASE_NOTES_SLACK_WEBHOOK }}
+        webhook-type: webhook-trigger
         payload: |
-          {
-            "version": "${{ github.event.client_payload.version }}",
-            "pull_request_url": "${{steps.cpr.outputs.pull-request-url}}"
-          }
-      env:
-        SLACK_WEBHOOK_URL: ${{ secrets.REPLICATED_SDK_RELEASE_NOTES_SLACK_WEBHOOK }}
+          version: "${{ github.event.client_payload.version }}"
+          pull_request_url: "${{steps.cpr.outputs.pull-request-url}}"

.github/workflows/vendor-portal-release-notes.yml

@@ -64,10 +64,8 @@ jobs:
       - name: Slack Notification
         uses: slackapi/[email protected]
         with:
+          webhook: ${{ secrets.VENDOR_PORTAL_RELEASE_NOTES_SLACK_WEBHOOK }}
+          webhook-type: webhook-trigger
           payload: |
-            {
-              "version": "${{ github.event.client_payload.version }}",
-              "pull_request_url": "${{ steps.cpr.outputs.pull-request-url }}"
-            }
-        env:
-          SLACK_WEBHOOK_URL: ${{ secrets.VENDOR_PORTAL_RELEASE_NOTES_SLACK_WEBHOOK }}
+            version: "${{ github.event.client_payload.version }}"
+            pull_request_url: "${{ steps.cpr.outputs.pull-request-url }}"

docs/enterprise/embedded-manage-nodes.mdx

@@ -10,7 +10,7 @@ Multi-node clusters with Embedded Cluster have the following limitations:
 
 * Support for multi-node clusters with Embedded Cluster is Beta. Only single-node embedded clusters are Generally Available (GA).
 
-* High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. To get access to this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
+* High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. For more information about this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
 
 * The same Embedded Cluster data directory used at installation is used for all nodes joined to the cluster. This is either the default `/var/lib/embedded-cluster` directory or the directory set with the [`--data-dir`](/reference/embedded-cluster-install#flags) flag. You cannot choose a different data directory for Embedded Cluster when joining nodes.
 
@@ -86,7 +86,7 @@ To add nodes to a cluster:
 Multi-node clusters are not highly available by default. The first node of the cluster is special and holds important data for Kubernetes and KOTS, such that the loss of this node would be catastrophic for the cluster. Enabling high availability (HA) requires that at least three controller nodes are present in the cluster. Users can enable HA when joining the third node.
 
 :::important
-High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. To get access to this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
+High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. For more information about this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
 :::
 
 ### HA Architecture
@@ -107,7 +107,7 @@ Enabling high availability has the following requirements:
 
 Enabling high availability has the following limitations:
 
-* High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. To get access to this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
+* High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. For more information about this feature, reach out to Alex Parker at [[email protected]](mailto:[email protected]).
 
 * The `--enable-ha` flag serves as a feature flag during the Alpha phase. In the future, the prompt about migrating to high availability will display automatically if the cluster is not yet HA and you are adding the third or more controller node. 
 
@@ -142,4 +142,4 @@ To create a multi-node HA cluster:
     ![high availability command line prompt](/images/embedded-cluster-ha-prompt.png)
     [View a larger version of this image](/images/embedded-cluster-ha-prompt.png)
 
-1. Wait for the migration to complete.
+1. Wait for the migration to complete.

docs/partials/embedded-cluster/_requirements.mdx

@@ -8,11 +8,9 @@
 
 * The disk on the host must have a maximum P99 write latency of 10 ms. This supports etcd performance and stability. For more information about the disk write latency requirements for etcd, see [Disks](https://etcd.io/docs/latest/op-guide/hardware/#disks) in _Hardware recommendations_ and [What does the etcd warning “failed to send out heartbeat on time” mean?](https://etcd.io/docs/latest/faq/) in the etcd documentation.
 
-* The filesystem at `/var/lib/embedded-cluster` has 40Gi or more of total space and must be less than 80% full
+* The data directory used by Embedded Cluster must have 40Gi or more of total space and be less than 80% full. By default, the data directory is `/var/lib/embedded-cluster`. The directory can be changed by passing the `--data-dir` flag with the Embedded Cluster `install` command. For more information, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).
 
-   The directory used for data storage can be changed by passing the `--data-dir` flag with the Embedded Cluster `install` command. For more information, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).
-
-   Note that in addition to the primary `/var/lib/embedded-cluster` directory, Embedded Cluster creates directories and files in the following locations:
+   Note that in addition to the primary data directory, Embedded Cluster creates directories and files in the following locations:
 
       - `/etc/cni`
       - `/etc/k0s`
@@ -31,6 +29,7 @@
       - `/var/lib/kubelet`
       - `/var/log/calico`
       - `/var/log/containers`
+      - `/var/log/embedded-cluster`
       - `/var/log/pods`
       - `/usr/local/bin/k0s`
 

docs/partials/kots/_download-portal-about.mdx

@@ -3,7 +3,7 @@
 dependencies:
 - name: replicated
   repository: oci://registry.replicated.com/library
-  version: 1.1.1
+  version: 1.2.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/partials/replicated-sdk/_dependency-yaml.mdx

@@ -0,0 +1 @@
+Template functions in the config context are available when rendering an application that includes the KOTS [Config](/reference/custom-resource-config) custom resource, which defines the KOTS Admin Console config screen. At execution time, template functions in the config context also can use the static context functions. For more information about configuring the Admin Console config screen, see [About the Configuration Screen](/vendor/config-screen-about).

docs/partials/template-functions/_config-context.mdx

@@ -0,0 +1,5 @@
+:::note
+The KOTS identity service feature is deprecated and is not available to new users.
+:::
+
+Template functions in the Identity context have access to Replicated KOTS identity service information.