#420 Adding canonical refs to ./getting-started part 7/10 (#626)

* canonicized choosing-a-rancher-version

* canonicized custom-ca-roo-certificate

* canonicized helm-version-requirments

* canonicized local-system-charts

* canonized update-rancher-certificate

* canonized upgrade-cert-manager

including pages pertaining to helm 2

* canonicized upgrade-and-rollback-kubernetes

* canonicized upgrade-kubernetes-without-upgrading-rancher
This commit is contained in:
Marty Hernandez Avedon
2023-05-25 17:25:14 -04:00
committed by GitHub
parent ee82ada796
commit a24c628687
34 changed files with 136 additions and 0 deletions
@@ -2,6 +2,10 @@
title: About Custom CA Root Certificates
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/custom-ca-root-certificates"/>
</head>
If you're using Rancher in an 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 a 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`.