Encrypting HTTP Communication
When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. You can then add the certificate to the ingress deployment.
Add SSL certificates to either projects, namespaces, or both. A project scoped certificate will be available in all its namespaces.
Prerequisites: You must have a TLS private key and certificate available to upload.
From the Global view, select the project where you want to deploy your ingress.
From the main menu, select Resources > Secrets > Certificates. Click Add Certificate. (For Rancher before v2.3, click Resources > Certificates.)
Enter a Name for the certificate.
Note: Kubernetes classifies SSL certificates as secrets, and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your SSL certificate must have a unique name among the other certificates, registries, and secrets within your project/workspace.
Select the Scope of the certificate.
Available to all namespaces in this project: The certificate is available for any deployment in any namespaces in the project.
Available to a single namespace: The certificate is only available for the deployments in one namespace. If you choose this option, select a Namespace from the drop-down list or click Add to a new namespace to add the certificate to a namespace you create on the fly.
From Private Key, either copy and paste your certificate's private key into the text box (include the header and footer), or click Read from a file to browse to the private key on your file system. If possible, we recommend using Read from a file to reduce likelihood of error.
Private key files end with an extension of
From Certificate, either copy and paste your certificate into the text box (include the header and footer), or click Read from a file to browse to the certificate on your file system. If possible, we recommend using Read from a file to reduce likelihood of error.
Certificate files end with an extension of
Result: Your certificate is added to the project or namespace. You can now add it to deployments.
- If you added an SSL certificate to the project, the certificate is available for deployments created in any project namespace.
- If you added an SSL certificate to a namespace, the certificate is available only for deployments in that namespace.
- Your certificate is added to the Resources > Secrets > Certificates view. (For Rancher before v2.3, it is added to Resources > Certificates.)
Now you can add the certificate when launching an ingress within the current project or namespace. For more information, see Adding Ingress.