A collection of certificates that software relies on when making TLS connections. The orchestrator needs one covering each server it contacts, and the VCF Installer must hold the Root CA certificates of any proxy.
Also called truststore.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains trust store in context, with comparison tables and the common traps.
Terms in this definition
- TLS
Transport Layer Security, the encryption protocol for traffic like HTTPS and Bastion sessions over port 443. On a storage account, minimumTlsVersion fixes the oldest accepted version without opening any network access.
- Orchestrator
Software, Kubernetes being an example, that looks after large numbers of containers throughout their life by scheduling, scaling, repairing and updating them.
- VCF Installer
Successor to Cloud Builder: either converges an existing vSphere environment into VCF or deploys from scratch a new VCF Instance or fleet, with its management domain and core components.
- Root CA
Sits at the top of a PKI as the ultimate source of trust. Microsoft Cloud PKI uses a two-tier design in which it signs the issuing CAs, with a lifetime anywhere between 5 and 25 years.
Related terms
- JRE
Bundled Java runtime inside the VCF Download Tool. If downloads pass through a proxy, add that proxy's certificate to the JRE trust store beforehand, otherwise they fail.
- PKI-based trust store
The recommended trust store for certificate-based authentication, holding each PKI's CAs in its own container (a maximum of 250 CAs at 8 KB apiece) and supporting issuer hints. Privileged Authentication Administrators manage it, and uploading a PKI in bulk needs P1 or P2.