Deploy the Software Stack

Google Cloud

ansible-playbook --vault-password-file ../.vault-pass.txt -i gcp_inventory.gcp.yml --extra-vars="type=gcp" deploy.yml

or Amazon AWS

ansible-playbook --vault-password-file ../.vault-pass.txt -i ec2.py --extra-vars="type=aws" deploy.yml

or Microsoft Azure (future)

ansible-playbook --vault-password-file ../.vault-pass.txt -i azure_rm.py --extra-vars="type=azure" deploy.yml

or VMware ESXi

ansible-playbook --vault-password-file ../.vault-pass.txt -i hosts --extra-vars="type=esx" deploy.yml

Review the populated contests in your site-directory

Note: The k8s master is tainted, which means that it does not run Kubernetes workload (which is best practice).

For that reason, services like Tiller and Rook-Ceph will initialize themselves only after workers did join the cluster. Therefore, the deploy.yml waits for the following condition to be met:

Number of rook-ceph-osd-#- pods equal count of worker nodes in the cluster

That typically takes in between two to three minutes. The deployment of Smart Check, Jenkins, etc. will take place after that initial initialization process.

Next Step (optional)

• Deploy the Endpoints
• [Deep Security]
• [Deep Security Smart Check]
• [Container Orchestration]
• [Container Runtimes]
• [Container Registry]
• [Cluster Storage]
• Jenkins
• GitLab
• [Linkerd]