Instructions: Private Install ​

When the Yellowbrick Deployer is launched from a public network, the infrastructure services it creates (such as networks and the managed Kubernetes service) must themselves be public so that it can reach them. It can't create a completely private network, disconnected from the internet, because then by definition it couldn't route to it.

These "public" installations still make sure that Yellowbrick Kubernetes workers are not routable from public networks, and access to object store is via private endpoints. However, if you need to make sure the platform in its entirety along with all infrastructure (such as gateways, load balancers or the Kubernetes API) are not public routable, you'll need to perform a fully private installation. This is a very common deployment scenario and one of the key reasons for choosing Yellowbrick.

To create a fully private installation, you must first build the networks and managed Kubernetes service, along with any private paths for accessing other cloud services such as object storage or cloud services APIs. You can integrate the new network into your corporate network as necessary. The infrastructure you create must be tagged so that the Deployer can discover it.

You then launch the Deployer from within that newly created private network and complete the installation using either the web application or the CLI.

Instructions on how to accomplish this across all public cloud providers, along with links to working Terraform examples, are included in this section.