starlingx/docs
Code Issues Proposed changes
Files
eede94e45dcb0b5e7cb4cb2c09da413d381003d5
docs/doc/source/usertasks/kubernetes/issuers-in-distributed-cloud-fbc035675c0f.rst
Ron Stone 749a8b7535 Fix usertask images (pick) 
Image location not readable in DS builds. Moved under kubernetes
Build cannot read image geometry metadata, causing :scale: option to fail. Removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I526e798bc22efc7efb03b81392825bb3ea9504f0
2021-11-02 14:45:02 +00:00

2.1 KiB
Raw Blame History

Issuers in Distributed Cloud

In a Distributed Cloud environment, end-user’s applications have a number of options for the cert-manager ISSUERs they use:

  • (Recommended) As part of your application deployment on each subcloud, create a cert-manager ISSUER for the External that you wish to use for signing your certificates.
    • The External -type ISSUER is configured exactly the same way for each of your application deployments on each subcloud, and
    • Your external clients need only trust a single External ’s public certificate.
  • As part of your application deployment on each subcloud, create a local internal RootCA ca ISSUER for signing your certificates.
    • The local internal RootCA ca ISSUER should ideally be slightly different (e.g. a unique subject) on each deployment, and
    • Your external clients need to trust each application deployment’s (on each subcloud) local internal RootCA public certificate.
    • This option is not ideal since this could mean 100s of RootCA Certificates.