diff --git a/docs/en/faq/removing-rancher/removing-rancher.md b/docs/en/faq/removing-rancher/removing-rancher.md index 617e6fcdfb9..33f41f44b49 100644 --- a/docs/en/faq/removing-rancher/removing-rancher.md +++ b/docs/en/faq/removing-rancher/removing-rancher.md @@ -25,7 +25,11 @@ The capability to access a downstream cluster without Rancher depends on the typ ### What if I don't want Rancher anymore? ->**Note:** The previously recommended [System Tools]({{}}/rancher/v2.6/en/system-tools/) has been deprecated since June 2022. +:::note + +The previously recommended [System Tools]({{}}/rancher/v2.6/en/system-tools/) has been deprecated since June 2022. + +::: If you [installed Rancher on a Kubernetes cluster,]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) remove Rancher by using the [Rancher Cleanup](https://github.com/rancher/rancher-cleanup) tool. diff --git a/docs/en/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md b/docs/en/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md index 6ae7aacc5f9..003174facc0 100644 --- a/docs/en/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md +++ b/docs/en/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md @@ -177,7 +177,11 @@ tls-san: For more information, refer to the [RKE2 documentation](https://docs.rke2.io/install/ha/). ->**Note:** RKE2 additionally provides a `resolv-conf` option for kubelets, which may help with configuring DNS in air-gap networks. +:::note + +RKE2 additionally provides a `resolv-conf` option for kubelets, which may help with configuring DNS in air-gap networks. + +::: ### 2. Create Registry YAML Create the registries.yaml file at `/etc/rancher/rke2/registries.yaml`. This will tell RKE2 the necessary details to connect to your private registry. diff --git a/docs/en/installation/resources/k8s-tutorials/aks/aks.md b/docs/en/installation/resources/k8s-tutorials/aks/aks.md index 81d563c65ff..c8f891eec54 100644 --- a/docs/en/installation/resources/k8s-tutorials/aks/aks.md +++ b/docs/en/installation/resources/k8s-tutorials/aks/aks.md @@ -50,7 +50,11 @@ az group create --name rancher-rg --location eastus To create an AKS cluster, run the following command. Use a VM size that applies to your use case. Refer to [this article](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes) for available sizes and options. When choosing a Kubernetes version, be sure to first consult the [support matrix](https://rancher.com/support-matrix/) to find the highest version of Kubernetes that has been validated for your Rancher version. -**Note:** If the version of Kubernetes is updated to v1.22 or later, the version of ingress-nginx would also need to be [updated](https://kubernetes.github.io/ingress-nginx/#faq-migration-to-apiversion-networkingk8siov1). +:::note + +If the version of Kubernetes is updated to v1.22 or later, the version of ingress-nginx would also need to be [updated](https://kubernetes.github.io/ingress-nginx/#faq-migration-to-apiversion-networkingk8siov1). + +::: ``` az aks create \ diff --git a/docs/en/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md b/docs/en/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md index f317b012aa7..3338dba4646 100644 --- a/docs/en/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md +++ b/docs/en/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md @@ -14,8 +14,11 @@ To address these changes, this guide will do two things: 1. Document the procedure for upgrading cert-manager 1. Explain the cert-manager API changes and link to cert-manager's official documentation for migrating your data -> **Important:** -> If you are upgrading cert-manager to the latest version from a version older than 1.5, follow the steps in [Option C](#option-c-upgrade-to-new-cert-manager-from-versions-15-and-below) below to do so. Note that you do not need to reinstall Rancher to perform this upgrade. +:::note Important: + +If you are upgrading cert-manager to the latest version from a version older than 1.5, follow the steps in [Option C](#option-c-upgrade-to-new-cert-manager-from-versions-15-and-below) below to do so. Note that you do not need to reinstall Rancher to perform this upgrade. + +::: # Upgrade Cert-Manager @@ -161,8 +164,11 @@ Before you can perform the upgrade, you must prepare your air gapped environment issuer,clusterissuer,certificates,certificaterequests > cert-manager-backup.yaml ``` - > **Important:** - > If you are upgrading from a version older than 0.11.0, Update the apiVersion on all your backed up resources from `certmanager.k8s.io/v1alpha1` to `cert-manager.io/v1alpha2`. If you use any cert-manager annotations on any of your other resources, you will need to update them to reflect the new API group. For details, refer to the documentation on [additional annotation changes.](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/#additional-annotation-changes) + :::note Important: + + If you are upgrading from a version older than 0.11.0, Update the apiVersion on all your backed up resources from `certmanager.k8s.io/v1alpha1` to `cert-manager.io/v1alpha2`. If you use any cert-manager annotations on any of your other resources, you will need to update them to reflect the new API group. For details, refer to the documentation on [additional annotation changes.](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/#additional-annotation-changes) + + ::: 1. Delete the existing cert-manager installation diff --git a/docs/en/quick-start-guide/deployment/outscale-qs/outscale-qs.md b/docs/en/quick-start-guide/deployment/outscale-qs/outscale-qs.md index 0263759fc12..c48c64f5efa 100644 --- a/docs/en/quick-start-guide/deployment/outscale-qs/outscale-qs.md +++ b/docs/en/quick-start-guide/deployment/outscale-qs/outscale-qs.md @@ -5,12 +5,19 @@ weight: 140 --- The following steps will quickly deploy a Rancher server on Outscale in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). +:::note + +The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). + +::: ## Prerequisites ->**Note** ->Deploying to Outscale will incur charges. +:::caution + +Deploying to Outscale will incur charges. + +::: - [Outscale Account](https://en.outscale.com/): You will require an account on Outscale as this is where the server and cluster will run. - [Outscale Access Key](https://docs.outscale.com/en/userguide/About-Access-Keys.html): Use these instructions to create an Outscale Access Key if you don't have one. diff --git a/docs/en/system-tools/system-tools.md b/docs/en/system-tools/system-tools.md index 2cbb45a4cf3..f237773e479 100644 --- a/docs/en/system-tools/system-tools.md +++ b/docs/en/system-tools/system-tools.md @@ -3,8 +3,11 @@ title: System Tools weight: 22 --- ->**Note:** System Tools has been deprecated since June 2022. +:::note +System Tools has been deprecated since June 2022. + +::: # Logs Please use [logs-collector](https://github.com/rancherlabs/support-tools/tree/master/collection/rancher/v2.x/logs-collector) to collect logs from your cluster. @@ -13,7 +16,11 @@ Please use [logs-collector](https://github.com/rancherlabs/support-tools/tree/ma If you want to replicate the stats command, you can run the following command on your cluster nodes: ->**Note:** This command requires the package `sysstat` on the cluster node. +:::note + +This command below requires the package `sysstat` on the cluster node. + +::: ``` /usr/bin/sar -u -r -F 1 1