public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-28 05:59:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

#384 Clarify which CA certs are needed

Browse Source
This commit is contained in:
Billy Tat
2023-01-31 11:18:15 -08:00
parent f9e6d8dc21
commit ee7d33740b
5 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/installation-and-upgrade/resources/add-tls-secrets.md
+2 -2
View File
@@ -25,9 +25,9 @@ If you want to replace the certificate, you can delete the `tls-rancher-ingress`
## Using a Private CA Signed Certificate ## Using a Private CA Signed Certificate
If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. If you are using a private CA, Rancher requires a copy of the private CA's root certificate or certificate chain, which the Rancher Agent uses to validate the connection to the server.
Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. Create a file named `cacerts.pem` that only contains the root CA certificate or certificate chain from your private CA, and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
``` ```
kubectl -n cattle-system create secret generic tls-ca \ kubectl -n cattle-system create secret generic tls-ca \
versioned_docs/version-2.0-2.4/getting-started/installation-and-upgrade/advanced-options/advanced-use-cases/helm2/helm-rancher/tls-secrets.md
+2 -2
View File
@@ -19,9 +19,9 @@ kubectl -n cattle-system create secret tls tls-rancher-ingress \
### Using a Private CA Signed Certificate ### Using a Private CA Signed Certificate
If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. If you are using a private CA, Rancher requires a copy of the private CA's root certificate or certificate chain, which the Rancher Agent uses to validate the connection to the server.
Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. Create a file named `cacerts.pem` that only contains the root CA certificate or certificate chain from your private CA, and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
>**Important:** Make sure the file is called `cacerts.pem` as Rancher uses that filename to configure the CA certificate. >**Important:** Make sure the file is called `cacerts.pem` as Rancher uses that filename to configure the CA certificate.
versioned_docs/version-2.0-2.4/getting-started/installation-and-upgrade/resources/add-tls-secrets.md
+2 -2
View File
@@ -21,9 +21,9 @@ kubectl -n cattle-system create secret tls tls-rancher-ingress \
## Using a Private CA Signed Certificate ## Using a Private CA Signed Certificate
If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. If you are using a private CA, Rancher requires a copy of the private CA's root certificate or certificate chain, which the Rancher Agent uses to validate the connection to the server.
Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. Create a file named `cacerts.pem` that only contains the root CA certificate or certificate chain from your private CA, and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
``` ```
kubectl -n cattle-system create secret generic tls-ca \ kubectl -n cattle-system create secret generic tls-ca \
versioned_docs/version-2.5/getting-started/installation-and-upgrade/resources/add-tls-secrets.md
+2 -2
View File
@@ -21,9 +21,9 @@ kubectl -n cattle-system create secret tls tls-rancher-ingress \
## Using a Private CA Signed Certificate ## Using a Private CA Signed Certificate
If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. If you are using a private CA, Rancher requires a copy of the private CA's root certificate or certificate chain, which the Rancher Agent uses to validate the connection to the server.
Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. Create a file named `cacerts.pem` that only contains the root CA certificate or certificate chain from your private CA, and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
``` ```
kubectl -n cattle-system create secret generic tls-ca \ kubectl -n cattle-system create secret generic tls-ca \
versioned_docs/version-2.6/getting-started/installation-and-upgrade/resources/add-tls-secrets.md
+2 -2
View File
@@ -25,9 +25,9 @@ If you want to replace the certificate, you can delete the `tls-rancher-ingress`
## Using a Private CA Signed Certificate ## Using a Private CA Signed Certificate
If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. If you are using a private CA, Rancher requires a copy of the private CA's root certificate or certificate chain, which the Rancher Agent uses to validate the connection to the server.
Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. Create a file named `cacerts.pem` that only contains the root CA certificate or certificate chain from your private CA, and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
``` ```
kubectl -n cattle-system create secret generic tls-ca \ kubectl -n cattle-system create secret generic tls-ca \