[Cloud] Deploy Kubernetes to GCP & AWS with boxing & unboxing container images

GDG Reading & Thames Valley
Tue, Sep 4, 2018, 6:30 PM (BST)

About this event

The venue is Central Working in central Reading. Very easy access to the train station. If arriving by car please allow time for traffic and parking. Any questions on the venue please either ask below or message us directly.

We have Safewrd Cloud Solution Consultant Christian Jantz coming all the way from Dresden. https://www.safewrd.com/

Christian Jantz
Open Source person since the early days by joining Fedora Linux who ended up doing cloudy things. After starting his adulthood in a media agency, he quickly left to experience startup world to teach them agile and DevOps thinking. Right now he is climbing some rocks, playing with containers, scaling clouds and teaching things to both startups and multinational corporations.

1. Deploying Kubernetes to cloud environments
Kubernetes is rising in traction and replaces all sorts of deployment practices in the market. But in order for your developers to get started using it, a running cluster would be step zero for them and step one for you as an operator.

In this introduction we will go through some cloud vendors like Google Cloud and AWS and talk about different ways to deploy Kubernetes in those environments. We will talk about Google Kubernetes Service (GKE), Amazon Elastic Kubernetes Service (EKS), kubeadm and kops to name a few of the tools we will look into.

2. Unboxing and boxing container images
Everyone wants to use containers today yet most don't really know how they function and what is in the box. Also building containers in unprivileged contexts can be challenging. In this talk we will look into a docker image and discuss how to create those packages using tools like kaniko ---- For most people that want to create a docker image the journey ends with docker build. What this will trigger is building a docker image using the running docker engine on your host. The problems start at a point where you don't have access to the docker daemon, want to build a container in a container (as most CI systems execute in containers nowadays) or just have limited permissions on the system. For this we will open the mystical box of a docker image by looking into: - Layers - Empty Layers - Configuration Details. Then we will look into the kaniko project that tries to build those images without ever touching a docker daemon to better understand how those images can be created and how to work in more restricted environments. Those information can also be very helpful when looking into container security and scanning what is in the box.