From 4a6721f6ab8afed2079e3b2e930bd1c7dfedf154 Mon Sep 17 00:00:00 2001 From: martyav Date: Tue, 17 Sep 2024 16:30:17 -0400 Subject: [PATCH] fixed expired-webhook-certificate-rotation.md --- .../expired-webhook-certificate-rotation.md | 5 +++-- .../expired-webhook-certificate-rotation.md | 5 +++-- .../expired-webhook-certificate-rotation.md | 5 +++-- .../expired-webhook-certificate-rotation.md | 5 +++-- .../expired-webhook-certificate-rotation.md | 5 +++-- .../expired-webhook-certificate-rotation.md | 5 +++-- 6 files changed, 18 insertions(+), 12 deletions(-) diff --git a/docs/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/docs/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 106479c0bb7..fc8e957c4af 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/docs/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. diff --git a/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 601d062984d..fab6d5db287 100644 --- a/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.5.12 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.5.11 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. diff --git a/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 106479c0bb7..fc8e957c4af 100644 --- a/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. diff --git a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 106479c0bb7..fc8e957c4af 100644 --- a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. diff --git a/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 106479c0bb7..fc8e957c4af 100644 --- a/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. diff --git a/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md b/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md index 106479c0bb7..fc8e957c4af 100644 --- a/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md +++ b/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md @@ -10,14 +10,15 @@ For Rancher versions that have `rancher-webhook` installed, certain versions cre In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue: -##### 1. Users with cluster access, run the following commands: +## 1. Users with Cluster Access, Run the Following Commands: + ``` kubectl delete secret -n cattle-system cattle-webhook-tls kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io kubectl delete pod -n cattle-system -l app=rancher-webhook ``` -##### 2. Users with no cluster access via `kubectl`: +## 2. Users with No Cluster Access Via `kubectl`: 1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster.