forked from try-bridgecrew/kubernetes-goat
-
Notifications
You must be signed in to change notification settings - Fork 3
/
setup-kubernetes-goat.sh
54 lines (47 loc) · 1.88 KB
/
setup-kubernetes-goat.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
#!/bin/bash
# Author: Madhu Akula
# This program has been created as part of Kuberentes Goat
# Kuberentes Goat setup and manage vulnerable infrastrcuture
# Checking kubectl setup
kubectl version --short > /dev/null 2>&1
if [ $? -eq 0 ];
then
echo "kubectl setup looks good."
else
echo "Error: Could not find kubectl or an other error happend, please check kubectl setup."
exit;
fi
# Checking helm2 setup
helm2 --help > /dev/null 2>&1
if [ $? -eq 0 ];
then
echo "helm2 setup looks good."
else
echo "Error: Could not find helm2, please check helm2 setup."
exit;
fi
# helm2 setup
echo "setting up helm2 rbac account and initialise tiller"
kubectl apply -f scenarios/helm2-rbac/setup.yaml
helm2 init --service-account tiller
# wait for tiller service to ready
echo "waiting for helm2 tiller service to be active."
sleep 50
# deploying helm chart to verify the setup
echo "deploying helm chart metadata-db scenario"
helm2 install --name metadata-db scenarios/metadata-db/
# setup the scenarios/configurations
echo 'deploying the vulnerable scenarios manifests'
kubectl apply -f scenarios/batch-check/job.yaml
kubectl apply -f scenarios/build-code/deployment.yaml
kubectl apply -f scenarios/cache-store/deployment.yaml
kubectl apply -f scenarios/health-check/deployment.yaml
kubectl apply -f scenarios/hunger-check/deployment.yaml
kubectl apply -f scenarios/internal-proxy/deployment.yaml
kubectl apply -f scenarios/kubernetes-goat-home/deployment.yaml
kubectl apply -f scenarios/poor-registry/deployment.yaml
kubectl apply -f scenarios/system-monitor/deployment.yaml
kubectl apply -f scenarios/hidden-in-layers/deployment.yaml
echo 'Successfully deployed Kubernetes Goat. Have fun learning Kubernetes Security!'
echo 'Ensure pods are in running status before running access-kubernetes-goat.sh script'
echo 'Now run the bash access-kubernetes-goat.sh to access the Kubernetes Goat environment.'