From 304fbc7944d8ba376c2205e173b5f3e42870187f Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 26 Aug 2024 06:28:32 -0400 Subject: [PATCH 1/5] Update versions table - v2.8.7 --- src/pages/versions.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/src/pages/versions.md b/src/pages/versions.md index 08101635102..f3b7dcf2ebb 100644 --- a/src/pages/versions.md +++ b/src/pages/versions.md @@ -39,9 +39,9 @@ Here you can find links to supporting documentation for the current released ver Community - v2.8.6 + v2.8.7 Documentation - Release Notes + Release Notes
N/A
✓
N/A
@@ -98,6 +98,14 @@ Here you can find links to supporting documentation for previous versions of Ran Support Matrix Prime Community + + + v2.8.6 + Documentation + Release Notes +
N/A
+
✓
+
N/A
v2.8.5 From 8d50cb4cb825a85b7a30ad1809036d6f07067431 Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 26 Aug 2024 06:47:17 -0400 Subject: [PATCH 2/5] [v2.8.7] Update Webhook Table --- versioned_docs/version-2.8/reference-guides/rancher-webhook.md | 1 + 1 file changed, 1 insertion(+) diff --git a/versioned_docs/version-2.8/reference-guides/rancher-webhook.md b/versioned_docs/version-2.8/reference-guides/rancher-webhook.md index 093fa07eb0c..a2ac995a62f 100644 --- a/versioned_docs/version-2.8/reference-guides/rancher-webhook.md +++ b/versioned_docs/version-2.8/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.8.7 | v0.4.10 | ✓ | ✗ | | v2.8.6 | v0.4.9 | ✓ | ✗ | | v2.8.5 | v0.4.7 | ✓ | ✓ | | v2.8.4 | v0.4.5 | ✓ | ✓ | From 7d51fdb720718e98c7fa3426fee88d279fce7da1 Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 26 Aug 2024 07:31:00 -0400 Subject: [PATCH 3/5] [v2.8.7] Update CSP Adapter Table --- .../cloud-marketplace/aws-cloud-marketplace/install-adapter.md | 1 + 1 file changed, 1 insertion(+) diff --git a/versioned_docs/version-2.8/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/versioned_docs/version-2.8/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index eb90ebce37a..d935d3de350 100644 --- a/versioned_docs/version-2.8/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/versioned_docs/version-2.8/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -19,6 +19,7 @@ In order to deploy and run the adapter successfully, you need to ensure its vers | Rancher Version | Adapter Version | |-----------------|:----------------:| +| v2.8.7 | v103.0.1+up3.0.1 | | v2.8.6 | v103.0.1+up3.0.1 | | v2.8.5 | v103.0.1+up3.0.1 | | v2.8.4 | v103.0.1+up3.0.1 | From 80402348822d2ed70d6b5f1192982418cc5b8086 Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 26 Aug 2024 08:08:51 -0400 Subject: [PATCH 4/5] [v2.8.7] Update Deprecations Table --- versioned_docs/version-2.8/faq/deprecated-features.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-2.8/faq/deprecated-features.md b/versioned_docs/version-2.8/faq/deprecated-features.md index bacef3e412e..37ba9a9cea1 100644 --- a/versioned_docs/version-2.8/faq/deprecated-features.md +++ b/versioned_docs/version-2.8/faq/deprecated-features.md @@ -16,8 +16,9 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| -| [2.8.6](https://github.com/rancher/rancher/releases/tag/v2.8.6) | July 31, 2024 | -| [2.8.5](https://github.com/rancher/rancher/releases/tag/v2.8.5) | June 17, 2024 | +| [2.8.7](https://github.com/rancher/rancher/releases/tag/v2.8.7) | Aug 26, 2024 | +| [2.8.6](https://github.com/rancher/rancher/releases/tag/v2.8.6) | Jul 31, 2024 | +| [2.8.5](https://github.com/rancher/rancher/releases/tag/v2.8.5) | Jun 17, 2024 | | [2.8.4](https://github.com/rancher/rancher/releases/tag/v2.8.4) | May 16, 2024 | | [2.8.3](https://github.com/rancher/rancher/releases/tag/v2.8.3) | Mar 28, 2024 | | [2.8.2](https://github.com/rancher/rancher/releases/tag/v2.8.2) | Feb 8, 2024 | From ea245e3f5b682c14c2b760c919f9ed0d9629a157 Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Mon, 26 Aug 2024 10:03:09 -0400 Subject: [PATCH 5/5] [v2.8.7] Update from main to keep working branch PRs less messy to review (#1443) * Use crds.enabled to install cert-manager Signed-off-by: Dharmit Shah * versioned * reverted changes to earliest versions and slightly modified comment * spacing issue --------- Signed-off-by: Dharmit Shah Co-authored-by: Dharmit Shah Co-authored-by: Billy Tat --- .../install-upgrade-on-a-kubernetes-cluster.md | 4 ++-- .../install-upgrade-on-a-kubernetes-cluster.md | 4 ++-- .../install-upgrade-on-a-kubernetes-cluster.md | 4 ++-- .../install-upgrade-on-a-kubernetes-cluster.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md index a8fa6fd51cc..8ccdb43d1bf 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md @@ -148,7 +148,7 @@ To see options on how to customize the cert-manager install (including for cases ::: ``` -# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: +# If you have installed the CRDs manually, instead of setting `installCRDs` or `crds.enabled` to `true` in your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download//cert-manager.crds.yaml # Add the Jetstack Helm repository @@ -161,7 +161,7 @@ helm repo update helm install cert-manager jetstack/cert-manager \ --namespace cert-manager \ --create-namespace \ - --set installCRDs=true + --set crds.enabled=true ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: diff --git a/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md b/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md index 8d367774725..cede46f04d0 100644 --- a/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md +++ b/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md @@ -148,7 +148,7 @@ To see options on how to customize the cert-manager install (including for cases ::: ``` -# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: +# If you have installed the CRDs manually, instead of setting `installCRDs` or `crds.enabled` to `true` in your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download//cert-manager.crds.yaml # Add the Jetstack Helm repository @@ -161,7 +161,7 @@ helm repo update helm install cert-manager jetstack/cert-manager \ --namespace cert-manager \ --create-namespace \ - --set installCRDs=true + --set crds.enabled=true ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: diff --git a/versioned_docs/version-2.8/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md b/versioned_docs/version-2.8/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md index 2ca5266315e..885c00f81dd 100644 --- a/versioned_docs/version-2.8/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md +++ b/versioned_docs/version-2.8/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md @@ -148,7 +148,7 @@ To see options on how to customize the cert-manager install (including for cases ::: ``` -# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: +# If you have installed the CRDs manually, instead of setting `installCRDs` or `crds.enabled` to `true` in your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download//cert-manager.crds.yaml # Add the Jetstack Helm repository @@ -161,7 +161,7 @@ helm repo update helm install cert-manager jetstack/cert-manager \ --namespace cert-manager \ --create-namespace \ - --set installCRDs=true + --set crds.enabled=true ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: diff --git a/versioned_docs/version-2.9/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md b/versioned_docs/version-2.9/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md index a8fa6fd51cc..8ccdb43d1bf 100644 --- a/versioned_docs/version-2.9/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md +++ b/versioned_docs/version-2.9/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md @@ -148,7 +148,7 @@ To see options on how to customize the cert-manager install (including for cases ::: ``` -# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: +# If you have installed the CRDs manually, instead of setting `installCRDs` or `crds.enabled` to `true` in your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download//cert-manager.crds.yaml # Add the Jetstack Helm repository @@ -161,7 +161,7 @@ helm repo update helm install cert-manager jetstack/cert-manager \ --namespace cert-manager \ --create-namespace \ - --set installCRDs=true + --set crds.enabled=true ``` Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: