public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 21:18:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

move where custom ca lives

Browse Source
This commit is contained in:
Denise Schannon
2018-09-11 20:37:36 -07:00
committed by Denise
parent 5c0c34f3e9
commit ec2c770bea
2 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/single-node/custom-ca-root-certificate/_index.md → content/rancher/v2.x/en/admin-settings/custom-ca-root-certificate/_index.md
+1 -1
View File
@@ -4,7 +4,7 @@ weight: 252
aliases: aliases:
- /rancher/v2.x/en/installation/custom-ca-root-certificate/ - /rancher/v2.x/en/installation/custom-ca-root-certificate/
--- ---
If you're using Rancher in a internal production environment where you aren't exposing apps publicly, use a certificate from a private certificate authority (CA). If you're using Rancher in a internal production environment where you aren't exposing apps publicly, use a certificate from a private certificate authority (CA).
Services that Rancher needs to access are sometimes configured with a certificate from an custom/internal CA root, also known as self signed certificate. If the presented certificate from the service cannot be validated by Rancher, the following error displays: `x509: certificate signed by unknown authority`. Services that Rancher needs to access are sometimes configured with a certificate from an custom/internal CA root, also known as self signed certificate. If the presented certificate from the service cannot be validated by Rancher, the following error displays: `x509: certificate signed by unknown authority`.
content/rancher/v2.x/en/installation/single-node/_index.md
+4 -5
View File
@@ -3,7 +3,6 @@ title: Single Node Install
weight: 250 weight: 250
aliases: aliases:
- /rancher/v2.x/en/installation/single-node-install/ - /rancher/v2.x/en/installation/single-node-install/
- /rancher/v2.x/en/installation/custom-ca-root-certificate/
--- ---
For development and testing environments, we recommend installing Rancher by running a single Docker container. In this installation scenario, you'll install Docker on a single Linux host, and then deploy Rancher on your host using a single Docker container. For development and testing environments, we recommend installing Rancher by running a single Docker container. In this installation scenario, you'll install Docker on a single Linux host, and then deploy Rancher on your host using a single Docker container.
@@ -21,7 +20,7 @@ For security purposes, SSL (Secure Sockets Layer) is required when using Rancher
>**Do you want to...** >**Do you want to...**
> >
>- Use a proxy? See [HTTP Proxy Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/proxy/) >- Use a proxy? See [HTTP Proxy Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/proxy/)
>- Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/custom-ca-root-certificate/) >- Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{< baseurl >}}/rancher/v2.x/en/admin-settings/custom-ca-root-certificate/)
>- Complete an Air Gap Installation? See [Air Gap](#air-gap) >- Complete an Air Gap Installation? See [Air Gap](#air-gap)
>- Record all transactions with the Rancher API? See [API Auditing](#api-auditing) >- Record all transactions with the Rancher API? See [API Auditing](#api-auditing)
> >
@@ -53,7 +52,7 @@ After creating your certificate, run the Docker command below to install Rancher
- Replace `<CERT_DIRECTORY>` with the directory path to your certificate file. - Replace `<CERT_DIRECTORY>` with the directory path to your certificate file.
- Replace `<FULL_CHAIN.pem>`,`<PRIVATE_KEY.pem>`, and `<CA_CERTS>` with your certificate names. - Replace `<FULL_CHAIN.pem>`,`<PRIVATE_KEY.pem>`, and `<CA_CERTS>` with your certificate names.
``` ```
docker run -d --restart=unless-stopped \ docker run -d --restart=unless-stopped \
-p 80:80 -p 443:443 \ -p 80:80 -p 443:443 \
-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \ -v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
@@ -83,7 +82,7 @@ docker run -d --restart=unless-stopped \
-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \ -v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
-v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \ -v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \
rancher/rancher:latest --no-cacerts rancher/rancher:latest --no-cacerts
``` ```
{{% /accordion %}} {{% /accordion %}}
{{% accordion id="option-d" label="Option D-Let's Encrypt Certificate" %}} {{% accordion id="option-d" label="Option D-Let's Encrypt Certificate" %}}
@@ -135,7 +134,7 @@ If you want to record all transations with the Rancher API, enable the [API Audi
If you are visiting this page to complete an [Air Gap Installation]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/), you must pre-pend your private registry URL to the server tag when running the installation command in the option that you choose. Add `<REGISTRY.DOMAIN.COM:PORT>` with your private registry URL in front of `rancher/rancher:latest`. If you are visiting this page to complete an [Air Gap Installation]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/), you must pre-pend your private registry URL to the server tag when running the installation command in the option that you choose. Add `<REGISTRY.DOMAIN.COM:PORT>` with your private registry URL in front of `rancher/rancher:latest`.
**Example:** **Example:**
<REGISTRY.DOMAIN.COM:PORT>/rancher/rancher:latest <REGISTRY.DOMAIN.COM:PORT>/rancher/rancher:latest
### Persistent Data ### Persistent Data