Deploying for Production

We use Civo for our production kubernetes hosting. We do this because their pricing is/was the most competitive at the time of development. As the project scales up, our host is subject to change.

1. Please follow these instructions to setup a civo environment locally: Setup Civo Environment
2. After your Civo Kubernetes environment is setup, we can secure our kubernetes services with SSL with this process: SSL Setup

By default, Civo uses Traefik as the proxy into our cluster. Our Ingress serves as the main entrypoint to our application.

We use a staging ingress that uses staging based TLS keys. These keys are, for all intents and purposes, useless outside of testing.

You can deploy the ingress using the following:

1. Confirm you are in the build directory:

   cd build

2. You can deploy using EITHER the make command OR kubectl
   1. make command:

      make k_deploy_ingress_staging

   2. kubectl:

      kubectl apply -f k8s/ingress-traefik-staging.yml

You can deploy the ingress using the following:

1. Confirm you are in the build directory:

   cd build

2. You can deploy using EITHER the make command OR kubectl
   1. make command:

      make k_deploy_ingress_prod

   2. kubectl:

      kubectl apply -f k8s/ingress-traefik-prod.yml

Confirm your ingress is up and running:

kubectl get ing
## Confirm you see 3 entries
# 1. cultivate-finance-base-ingress
# 2. cultivate-finance-ingress-www
# 3. cultivate-finance-ingress-base-dns

You can find the guide for deploying our web application to our kubernetes cluster here: Building and Running the Webapp in Kubernetes production

You can find the guide for deploying our Wiki documentation to our kubernetes cluster here: Building and Running the Wiki in Kubernetes production