Kubernetes configuration for running the checkers app environment.
- Have access to
kubectl
andhelm
from your command line - If you're running locally (rather than in gcloud, for example), ensure you have docker installed (and possibly minikube depending on your version of docker)
- Run
helm init
if you haven't installed Tiller on your cluster yet - Copy
values.example.yaml
tovalues.yaml
and fill in all the values for your environment - Ensure you have the domain you specified in your system's hosts file pointing at 127.0.0.1
- Run
helm dependency build
andhelm install .
from the root of this repo - After a few moments, the app should be running at your domain
If you already have gcloud on your system and have no problem switching kubeconfigs locally, you should just be able to follow the above instructions and deploy to a GKE cluster. However, if you aren't familiar with gcloud roles and
If you want a slightly more isolated approach, you can head to the /kubectl
directory where you have access to a container that has kubectl and gcloud already installed.
- Mount the local path to this repo in a
docker-compose.override.yaml
file. - Run
docker-compose up -d
from that directory - Run
docker exec -it kubectl bash
to get into the container - Head over to
cd /var/kube
If you've already set up your gcloud values.yaml, you can run ./gcloud_install
from the root. Otherwise if you want to do it manually and get stuck, that file is a good place to start figuring out what is needed to get it all running.
Modify the values.yaml
file to set prediction.nvidia_gpu
to true
. Make
If you're running ./gcloud_install
, that script will install the drivers for you. Otherwise, you should make sure you follow the Kubernetes instructions for scheduling GPUs to ensure the prediction container has access to the correct drivers and node pools.