airship/treasuremap
Code Issues Proposed changes

Update docs to clarify certificates requirements

Browse Source 
During the initial configuration it's required to
configure a set of valid certificates for ingress.
Make it more explicit so people don't miss this step.

Change-Id: Ie6477f934688467b7d5dfe1cc8191f6acff29a21
This commit is contained in:
Evgeny 2019-02-25 12:18:25 -08:00 committed by Kaspars Skels
parent efae9cd97f
commit 0aac1554cc
2 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/authoring_and_deployment.rst
View File

@ -351,6 +351,17 @@ with random generated ones:
python3 -c "from crypt import *; print(crypt('<YOUR_PASSWORD>', METHOD_SHA512))" python3 -c "from crypt import *; print(crypt('<YOUR_PASSWORD>', METHOD_SHA512))"
Configure certificates in ``site/${NEW_SITE}/secrets/certificates/ingress.yaml``,
they need to be issued for domain configured in a section ``data.dns.ingress_domain``
of a file ``./site/${NEW_SITE}/networks/common-addresses.yaml``. A list of endpoints
which will be used with these certificates can be found in the following file
``./site/${NEW_SITE}/software/config/endpoints.yaml``.
.. caution::
It's required to configure valid certificates, self-signed certificates
are not supported.
Manifest linting and combining layers Manifest linting and combining layers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4
site/airship-seaworthy/secrets/certificates/ingress.yaml
View File

@ -1,7 +1,7 @@
--- ---
# Example manifest for ingress cert. # Example manifest for ingress cert.
# Shall be replaced with proper/valid set. # NEWSITE-CHANGEME: must be replaced with proper/valid set,
# Self-signed certs are not supported. # self-signed certs are not supported.
metadata: metadata:
layeringDefinition: layeringDefinition:
abstract: false abstract: false