Synchronization getambassador.io ->ambassador-docs -- Nightly job - 2023-10-25

docs/cloud/latest/cloud-features.yml

@@ -1,9 +1,5 @@
 # Cloud features should be represented as objects, path always starting with '/' and ending without '/'.
 
-- {
-    path: /docs/cloud/latest/onboarding-dashboard,
-    feature: Team collaboration,
-  }
 - {
     path: /docs/cloud/latest/service-catalog/concepts/services,
     feature: Team collaboration,
@@ -20,10 +16,6 @@
     path: /docs/cloud/latest/service-catalog/howtos/cells,
     feature: Team collaboration,
   }
-- {
-    path: /docs/cloud/latest/onboarding-dashboard,
-    feature: Team collaboration,
-  }
 
 - {
     path: /docs/cloud/latest/service-catalog/howtos/intercept,

docs/cloud/latest/onboarding-dashboard/index.md

@@ -5,26 +5,24 @@ description: "In this section, you can see the ambassador onboarding procces of
 
 # Onboarding Dashboard
 
-A central location to see the status of your developers, and the services within your organization.
+A central location to check the status of your developers, or the count of telepresence connections to your clusters.
 
 ## Onboarding Overview
 
-All the members of your organization can look at the onboarding dashboard to see which invited developers haven't onboarded and which have. You can also invite new developers here, or see which services are in use across your organization.
+All members of your organization have the ability to access the dashboard, where they can clearly identify invited developers who have not yet joined, as well as those who have. Furthermore, from this dashboard, you can send invitations to new developers (excluding Developer and Lite subscriptions).
+In addition to this, easy access is provided to information about your clusters, as well as the features developed by Ambassador.
 
 <p align="center">
   <img src="../images/onboarding-dashboard.png" width="600" alt="Onboarding dashboard" />
 </p>
 
-<p align="center">
-  <img src="../images/onboarding-active-services.png" width="600" alt="Active services" />
-</p>
 
-<p align="center">
-  <img src="../images/onboarding-latest-intercepts.png" width="600" alt="Latest intercepts" />
-</p>
+- **Connects:** Total telepresence connections made to your clusters.
+- **Clusters:** Your clusters set up through Ambassador Cloud.
+- **Features:**  Additional functionalities that Ambassador provides for you and your organization.
 
+Team members section is  available for all subscriptions except Lite and Developer:
 - **Invite more people:** Invite your colleagues to collaborate, send an email invitation link to start the Ambassador Cloud experience.
 - **Re-Invite people:** Resend the invite to colleagues that didn't accept the first invite.
 - **Developers onboarded:** See the number of people that have created or initialized an intercept.
 - **Need to be onboarded:** List of people who have not created any intercept. You can nudge them to send some useful email with instructions about how to start.
-- **Active services:** Your services that are currently flagged as `active`, how they were activated, and the last seen date.

docs/cloud/latest/releaseNotes.yml

@@ -30,6 +30,12 @@
 
 changelog: ''
 items:
+  - date: '2023-10-02'
+    notes:
+      - title: 'Organization Dashboard redesign'
+        body: The Dashboard was redesigned to better highlight users and organization's usage of Telepresence and Edge Stack.
+        image: './new-organization-dashboard.png'
+        type: feature
   - date: '2023-08-29'
     notes:
       - title: 'New subscription plans'

docs/edge-stack/3.8/releaseNotes.yml

@@ -32,6 +32,21 @@
 
 changelog: https://github.com/datawire/edge-stack/blob/$branch$/CHANGELOG.md
 items:
+  - version: 3.8.2
+    date: '2023-10-11'
+    notes:
+      - title: Upgrade Envoy
+        type: security
+        body: >-
+          This release includes security patches to the current Envoy proxy version to address CVE 2023-44487 and includes a fix to determine if a client is making too many requests with premature resets. The connection is disconnected if more than 50 percent of resets are considered premature. Another fix is also included which exposes a runtime setting to control the limit on the number of HTTP requests processed from a single connection in a single I/O cycle to mitigate CPU starvation.
+        docs: topics/running/running/
+
+      - title: Upgrade Golang to 1.20.10
+        type: security
+        body: >-
+          Upgrading to the latest release of Golang as part of our general dependency upgrade process. This update resolves CVE-2023-39323 and CVE-2023-39325.
+        docs: https://go.dev/doc/devel/release#go1.20.minor
+
   - version: 3.8.1
     date: '2023-09-18'
     notes:

docs/edge-stack/3.8/versions.yml

@@ -2,24 +2,24 @@
 branch: release/v3.8
 
 # self
-version: 3.8.1
+version: 3.8.2
 productName: "Ambassador Edge Stack"
 productNamePlural: "Ambassador Edge Stacks"
 productNamespace: ambassador
 productDeploymentName: edge-stack
 productHelmName: edge-stack
 
 # OSS (not self)
-ossVersion: 3.8.1
+ossVersion: 3.8.2
 ossDocsVersion: "pre-release"
-ossChartVersion: 8.8.1
+ossChartVersion: 8.8.2
 OSSproductName: "Emissary-ingress"
 OSSproductNamePlural: "Emissary-ingresses"
 
 # AES (self)
-aesVersion: 3.8.1
+aesVersion: 3.8.2
 aesDocsVersion: "pre-release"
-aesChartVersion: 8.8.1
+aesChartVersion: 8.8.2
 AESproductName: "Ambassador Edge Stack"
 AESproductNamePlural: "Ambassador Edge Stacks"
 

docs/edge-stack/latest/about/aes-emissary-eol.md

@@ -0,0 +1,56 @@
+# $productName$ End of Life Policy
+
+This document describes the End of Life policy and maintenance windows for Ambassador Edge Stack, and to the open source project Emissary Ingress.
+
+## Supported Versions
+
+Ambassador Edge Stack and Emissary-ingress versions are expressed as **x.y.z**, where **x** is the major version, **y** is the minor version, and **z** is the patch version, following [Semantic Versioning](https://semver.org/) terminology.
+
+**X-series (Major Versions)**
+
+- **1.y**: 1.0 GA on January 2020
+- **2.y**: 2.0.4 GA on October 2021, and 2.1.0 in December 2021.
+
+**Y-release (Minor versions)**
+
+- For 1.y, that is **1.14.z**
+- For 2.y, that is **2.3.z**
+
+In this document, **Current** refers to the latest X-series release.
+
+Maintenance refers to the previous X-series release, including security and Sev1 defect patches.
+
+## CNCF Ecosystem Considerations
+
+- Envoy releases a major version every 3 months and supports its previous releases for 12 months. Envoy does not support any release longer than 12 months.
+- Kubernetes 1.19 and newer receive 12 months of patch support (The [Kubernetes Yearly Support Period](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/1498-kubernetes-yearly-support-period/README.md)).
+
+# The Policy
+
+> We will offer a 6 month maintenance window for the latest Y-release of an X-series after a new X-series goes GA and becomes the current release. For example, we will support 2.3 for severity 1 and defect patches for six months after 3.0 is released.
+>
+
+> During the maintenance window, Y-releases will only receive security and Sev1 defect patches. Users desiring new features or bug fixes for lower severity defects will need to upgrade to the current X-series.
+>
+
+> The current X-series will receive as many Y-releases as necessary and as often as we have new features or patches to release.
+>
+
+> Ambassador Labs offers no-downtime migration to current versions from maintenance releases. Migration from releases that are outside of the maintenance window may be subject to downtime.
+>
+
+> Artifacts of releases outside of the maintenance window will be frozen and will remain available publicly for download with the best effort. These artifacts include Docker images, application binaries, Helm charts, etc.
+>
+
+### When we say support with “defect patches”, what do we mean?
+
+- We will fix security issues in our Emissary-ingress and Ambassador Edge Stack code
+- We will pick up security fixes from dependencies as they are made available
+- We will not maintain forks of our major dependencies
+- We will not attempt our own back ports of critical fixes to dependencies which are out of support from their own communities
+
+## Extended Maintenance for 1.14
+
+Given this policy, we should have dropped maintenance for 1.14 in March 2022, however we recognize that the introduction of an EOL policy necessitates a longer maintenance window. For this reason, we do offer an "extended maintenance" window for 1.14 until the end of September 2022, 3 months after the latest 2.3 release. Please note that this extended maintenance window will not apply to customers using Kubernetes 1.22 and above, and this extended maintenance will also not provide a no-downtime migration path from 1.14 to 3.0.
+
+After September 2022, the current series will be 3.x, and the maintenance series will be 2.y.