ddd6e17f70
validation=false on the cert-manager namespace Signed-off-by: JoshVanL <vleeuwenjoshua@gmail.com>
83 lines
3.1 KiB
ReStructuredText
83 lines
3.1 KiB
ReStructuredText
=======================
|
|
Installing on OpenShift
|
|
=======================
|
|
|
|
cert-manager supports running on OpenShift in a similar manner to :doc:`Running on Kubernetes <./kubernetes>`.
|
|
It runs within your OpenShift cluster as a series of deployment
|
|
resources.
|
|
It utilises `CustomResourceDefinitions`_ to configure Certificate
|
|
Authorities and request certificates.
|
|
|
|
It is deployed using regular YAML manifests, like any other application on
|
|
OpenShift.
|
|
|
|
Once cert-manager has been deployed, you must configure Issuer or ClusterIssuer
|
|
resources which represent certificate authorities.
|
|
More information on configuring different Issuer types can be found in the
|
|
:doc:`respective setup guides </tasks/issuers/index>`.
|
|
|
|
.. warning::
|
|
|
|
You should not install multiple instances of cert-manager on a single
|
|
cluster. This will lead to undefined behaviour and you may be banned from
|
|
providers such as Let's Encrypt.
|
|
|
|
Login to your OpenShift cluster
|
|
===============================
|
|
|
|
Before you can install cert-manager, you must first ensure your local machine
|
|
is configured to talk to your OpenShift cluster using the ``oc`` tool.
|
|
|
|
.. code-block:: shell
|
|
|
|
# Login to the OpenShift cluster as the system:admin user
|
|
oc login -u system:admin
|
|
|
|
Installing with regular manifests
|
|
=================================
|
|
|
|
In order to install cert-manager, we must first create a namespace to run it
|
|
within. This guide will install cert-manager into the ``cert-manager``
|
|
namespace. It is possible to run cert-manager in a different namespace,
|
|
although you will need to make modifications to the deployment manifests.
|
|
|
|
.. code-block:: shell
|
|
|
|
# Create a namespace to run cert-manager in
|
|
oc create namespace cert-manager
|
|
|
|
We can now go ahead and install cert-manager. All resources
|
|
(the CustomResourceDefinitions, cert-manager, and the webhook component)
|
|
are included in a single YAML manifest file:
|
|
|
|
.. code-block:: shell
|
|
|
|
# Install the CustomResourceDefinitions and cert-manager itself
|
|
oc apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v0.11.0-alpha.0/cert-manager-openshift.yaml
|
|
|
|
.. note::
|
|
The ``--validate=false`` flag is added to the ``oc apply`` command above
|
|
else you will receive a validation error relating to the ``caBundle`` field
|
|
of the ``ValidatingWebhookConfiguration`` resource.
|
|
|
|
|
|
Configuring your first Issuer
|
|
=============================
|
|
|
|
Before you can begin issuing certificates, you must configure at least one
|
|
Issuer or ClusterIssuer resource in your cluster.
|
|
|
|
You should read the :doc:`Setting up Issuers </tasks/issuers/index>` guide to
|
|
learn how to configure cert-manager to issue certificates from one of the
|
|
supported backends.
|
|
|
|
Debugging installation issues
|
|
=============================
|
|
|
|
If you have any issues with your installation, please refer to the
|
|
:doc:`troubleshooting guide <../troubleshooting>`.
|
|
|
|
.. _`CustomResourceDefinitions`: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
|
|
.. _`kubernetes/kubernetes#69590`: https://github.com/kubernetes/kubernetes/issues/69590
|
|
.. _`ValidatingWebhookConfiguration`: https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/
|