itsouvalas

Introduction

In the following lines we will go through each step required to deploy cf-k8s-controllers using the documentation already in place and provide a list of commands as a runbook along with additions that may come up during the process.

Prerequisites

• kubectl
• kubernetes cluster of one of the upstream releases
• container registry - in this example we are using dockerhub
• cf cli version 8.1 or greater

itsouvalas

Introduction

So you’ve successfully deployed your cloudfoundry application using the deployment managed by your beloved cf-genesis-kit, you’ve set up your cloudfoundry app-autoscaling using the respective cf-app-autoscaler-genesis-kit and you’ve been blissfully living your life worry free using cf and genesis clis. Given that blissfully is rarely a word that describes your devops life, this dream state of yours has been brutally interrupted by your team which has secretly been developing a branch that takes advantage of messaging. You are now responsible for making that happen within the cloudfoundry ecosystem - the pros outway the cons and there are no backsies! You quickly start your research on the topic and voila, you land on thi

itsouvalas

Introduction

In the following documentation we will go through all the steps required to use cf-for-k8s under AWS provisioned kubernetes service, specifically EKS. As most documentation endeavors already exist in some way or another, this is mostly based on cf-for-k8s readme and the in-depth guide of Deploying CF for K8s. At this stage of writing and to expedite the process, we will be using direct links as sources when appropriate, with the intent to integrate them in this document and keep the references. The rest of the documentation will focus on the missing pieces that should get you running out of the box without having to do your own research.

Prerequisites

• https://cf-for-k8s.io/docs/deploying/#prerequisites

• AWS cli

• [Configure your AWS cli to use your IAM credentials]

itsouvalas

Prerequisites

Bosh

cd /usr/bin/

wget https://github.com/cloudfoundry/bosh-cli/releases/download/v6.4.16/bosh-cli-6.4.16-linux-amd64

itsouvalas

Steps to reproduce

• Issue genesis deploy environment-name.yml on a cf-app-autoscaler-genesis-kit deployment directory
• Usually on first deploy we will receive the following output:

Task 128401 | 08:24:09 | L executing pre-start: asactors/1754d9a2-48a3-4005-8423-694b14f8422b (0) (canary) (00:04:08)
                       L Error: Action Failed get_task: Task 9d510210-3d7e-44d5-6d2a-7ce213fb535e result: 2 of 5 pre-start scripts failed. Failed Jobs: scalingengine, operator. Successful Jobs: bosh-dns, user_add, scheduler.
Task 128401 | 08:24:34 | Error: Action Failed get_task: Task 9d510210-3d7e-44d5-6d2a-7ce213fb535e result: 2 of 5 pre-start scripts failed. Failed Jobs: scalingengine, operator. Successful Jobs: bosh-dns, user_add, scheduler.

itsouvalas

502s the Why and How to address them

Introduction

Great Scott! You made to kubernetes! You've successfully deployed your application on a kubernetes cluster and you start to understand why all this fuzz about it. Aftet having statically scaled your deployment to a number of replicas/pods, you feel adventurous enough to use the all mighty Horizontal Pod Autoscaler. I mean, don't take me wrong, there's no harm in using a static scale to a number of your choosing, on the other hand, one of the beauties of using a container-orchestration system such us kubernetes is the music like results that stems from kubernetes directing the lead violinist (one pod) as well as tens or hundreds of violins (x pods) in absolute harmony!

So, there you have it, you bought into that music parallelism, and you