Playbooks

deployment to a clean infrastructure

General remarks:

GCP does not route any traffic to your services unless the service is "healthy". It might take a few minutes after startup before the services is classified as healthy. Until then you will only see some generic error message.

These are the steps to set up the build server on a clean infrastructure:

Configure the tools on your local machine:
```
./local_setup.sh
```

Delete the old cluster, if it still exists:

cd kubernetes/cluster
./cluster_delete.sh

Create the cluster:

cd kubernetes/cluster
./cluster_create.sh

Create the disk storage, if it does not yet exist:
```
cd kubernetes/cluster
./disk_create.sh
```

SSH into the VM instance mounting the volume, find the mount point and then set

# go to the mount point of the volume
cd  /var/lib/kubelet/plugins/kubernetes.io/gce-pd/mounts/jenkins-home
# change the permissions
sudo chmod a+rwx

Push the docker images to gcr.io:

cd containers
#for each subfolder:
./build_deploy.sh <foldername>

Deploy the stack:
```
cd kubernetes
./deploy.sh
```
Configure it

creating basic authentication for reverse proxy

create auth file, based on ingress-nginx documentation

cd kubernetes/reverse-proxy
htpasswd -c auth <username>
# enter password at prompt
# add more users as required
kubectl create secret generic proxy-auth --from-file=auth --namespace=jenkins

1.7 KiB Raw Blame History

Playbooks

deployment to a clean infrastructure

creating basic authentication for reverse proxy

1.7 KiB

Raw Blame History