Install CLI and Keptn

1. Install local tools

   • az

2. Make sure you are logged in to your Azure account with az login

3. Create AKS cluster

   • Master version: 1.15.x (tested version: 1.15.10)
   • One D8s_v3 node

1. Install local tools

   • AWS CLI (version >= 1.16.156)

2. Create EKS cluster on AWS

   • Master version: 1.15 (tested version: 1.15)
   • One m5.2xlarge node
   • Sample script using eksctl to create such a cluster

   eksctl create cluster --version=1.15 --name=keptn-cluster --node-type=m5.2xlarge --nodes=1 --region=eu-west-3
   

   Known bug in EKS 1.13

   Please note that for EKS version 1.13 in our testing we learned that the default CoreDNS that comes with certain EKS versions has a bug. In order to solve that issue we can use eksctl to update the CoreDNS service like this:

   eksctl utils update-coredns --name=keptn-cluster --region=eu-west-3 --approve
   

Run your Keptn installation for free on GKE! If you sign up for a Google Cloud account, Google gives you an initial $300 credit. For deploying Keptn you can apply for an additional $200 credit which you can use towards that GKE cluster needed to run Keptn.

Apply for your credit here

1. Install local tools

   • gcloud
   • python 2.7 (required for Ubuntu 19.04)

2. Create GKE cluster

   • Master version:: 1.15.x (tested version: 1.15.9-gke.22)
   • One n1-standard-8 node
   • Image type Ubuntu or COS (Note: If you plan to use Dynatrace monitoring, select ubuntu for a more convenient setup.)
   • Sample script to create such cluster:

   // set environment variables
   PROJECT=nameofgcloudproject
   CLUSTER_NAME=nameofcluster
   ZONE=us-central1-a
   REGION=us-central1
   GKE_VERSION="1.15"
   

   gcloud container clusters create $CLUSTER_NAME --project $PROJECT --zone $ZONE --no-enable-basic-auth --cluster-version $GKE_VERSION --machine-type "n1-standard-8" --image-type "UBUNTU" --disk-type "pd-standard" --disk-size "100" --metadata disable-legacy-endpoints=true --scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" --num-nodes "1" --enable-stackdriver-kubernetes --no-enable-ip-alias --network "projects/$PROJECT/global/networks/default" --subnetwork "projects/$PROJECT/regions/$REGION/subnetworks/default" --addons HorizontalPodAutoscaling,HttpLoadBalancing --no-enable-autoupgrade
   

1. Please note that you have to bring your own OpenShift cluster in version 3.11

2. Install local tools

   • oc CLI - v3.11

3. On the OpenShift master node, execute the following steps:

   • Set up the required permissions for your user:

   oc adm policy --as system:admin add-cluster-role-to-user cluster-admin <OPENSHIFT_USER_NAME>
   

   • Set up the required permissions for the installer pod:

   oc adm policy  add-cluster-role-to-user cluster-admin system:serviceaccount:default:default
   oc adm policy  add-cluster-role-to-user cluster-admin system:serviceaccount:kube-system:default
   

   • Enable admission WebHooks on your OpenShift master node:

   sudo -i
   cp -n /etc/origin/master/master-config.yaml /etc/origin/master/master-config.yaml.backup
   oc ex config patch /etc/origin/master/master-config.yaml --type=merge -p '{
     "admissionConfig": {
       "pluginConfig": {
         "ValidatingAdmissionWebhook": {
           "configuration": {
             "apiVersion": "apiserver.config.k8s.io/v1alpha1",
             "kind": "WebhookAdmission",
             "kubeConfigFile": "/dev/null"
           }
         },
         "MutatingAdmissionWebhook": {
           "configuration": {
             "apiVersion": "apiserver.config.k8s.io/v1alpha1",
             "kind": "WebhookAdmission",
             "kubeConfigFile": "/dev/null"
           }
         }
       }
     }
   }' >/etc/origin/master/master-config.yaml.patched
   if [ $? == 0 ]; then
     mv -f /etc/origin/master/master-config.yaml.patched /etc/origin/master/master-config.yaml
     /usr/local/bin/master-restart api && /usr/local/bin/master-restart controllers
   else
     exit
   fi
   

1. Install local tools

   • pks CLI - v1.0.4

2. Create PKS cluster on GCP

   • Use the provided instructions for Enterprise Pivotal Container Service (Enterprise PKS) installation on GCP

   • Create a PKS cluster by using the PKS CLI and executing the following command:

   // set environment variables
   CLUSTER_NAME=name_of_cluster
   HOST_NAME=host_name
   PLAN=small
   

   pks create-cluster $CLUSTER_NAME --external-hostname $HOST_NAME --plan $PLAN
   

Note: Please refer to the official homepage of K3s for detailed installation instructions. Within this page we only provide a very short guide on how we run Keptn on K3s.

1. Download, install K3s (tested with versions 1.16 to 1.18) and run K3s using the following command:

   curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.18.3+k3s1 K3S_KUBECONFIG_MODE="644" sh -s - --no-deploy=traefik
   

   This installs version v1.18.3+k3s1 (please refer to the K3s GitHub releases page for newer releases), sets file permissions 644 on /etc/rancher/k3s/k3s.yaml and disables traefik as an ingress controller.

2. Export the Kubernetes profile using

   export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
   

3. Verify that the connection to the cluster works

   kubectl get nodes   
   

1. Download and install Minikube (tested with versions 1.3 to 1.10).

2. Create a new Minikube profile (named keptn) with at least 6 CPU cores and 12 GB memory using:

   minikube start -p keptn --cpus 6 --memory 12200
   

3. (Optional) Start the Minikube LoadBalancer service in a second terminal by executing:

   minikube tunnel 
   

• mongoDb database for the Keptn’s log
• NATS cluster
• Keptn core services:
• api
• bridge
• configuration-service
• distributors
• eventbroker
• gatekeeper-service
• helm-service
• jmeter-service
• lighthouse-service
• mongodb-datastore
• remediation-service
• shipyard-service
• wait-service
• Services to deploy artifacts and to demonstrate the self-healing use cases:
• prometheus-service
• servicenow-service
• openshift-route-service (OpenShift only)