https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/Recent content in Certificates onHugo -- gohugo.ioTue, 06 Oct 2020 08:48:45 +0000https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/selfsingned/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/selfsingned/During installation, you configure certificates in the graphical interface at the permanent management cluster creation step. With a self-signed certificate, you do not need to install anything during installation. Screenshot of cluster creation with a self-signed certificate After installation completes and you open the Shturval platform in a web browser, you must accept the certificate: https://shturval.<shturval_cluster_name>.<base_domain>. where: <shturval_cluster_name> - IP address or Ingress of your management cluster; <base_domain> - your domain zone or shturval.https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/corpcert/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/corpcert/During installation, you configure certificates in the graphical interface at the permanent management cluster creation step. To install with a corporate certificate, create the certificate. Note OpenSSL version 3.0 or later is required for the commands to work correctly. Certificate cat > openssl-san.cnf <<EOF [req] default_bits = 2048 prompt = no default_md = sha256 req_extensions = req_ext distinguished_name = dn [ dn ] C=RU ST=Moscow L=Moscow O=My Company OU=Department emailAddress=admin@example.com CN = example.https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/intermediate/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/intermediate/If you have an intermediate certificate authority (Intermediate CA) certificate signed by your corporate certificate authority (Certificate Authority, CA), you can use it to issue certificates automatically with Cert-manager. During installation, you configure certificates in the graphical interface at the permanent management cluster creation step. During installation, you must: Upload the certificate chain in PEM format (your intermediate certificate -> corporate CA certificate). Upload the intermediate CA private key. You can provide the certificate and key by uploading files or entering the data as text.https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/acme/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/acme/During installation, you configure certificates in the graphical interface at the permanent management cluster creation step. With an ACME certificate, you must: Upload the ACME CA root certificate file. Specify the ACME server address with port and resource path. You can specify an email address associated with the ACME account. Note If the cluster uses an ACME certificate, monitor the ACME server. If the server fails, clusters with ACME certificates become unavailable.https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/letsencrypt/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/platform-admin/install/preparations/tls/letsencrypt/During installation, you configure certificates in the graphical interface at the permanent management cluster creation step. To create certificates with Let’s Encrypt, the ingress controller must be reachable from the Internet. At least one of the following must be true: The external load balancer must have a public IP address; A public IP address must be assigned for IngressVIP. With a Let’s Encrypt certificate, you must specify an email address associated with the account.