What it really means to create an on-premise cloud with Kubernetes. PeakIt.003

• Be patient if something goes south for the winter. (Interactive meetup)
• Recording. Live on baywatch.
• Demo gods prayer.

• Why ?! Does it worth it ?
• Drawbacks
• Setting up one minimal linux host for a node
• Continous Integration and Continous Deployment
• Kubectl for Dummies
• Rancher orchestrator
• LoadBalancers: Nginx
• Shared persistent data: Nfs
• Cert-manager: Jetstack

• Visual Studio Code setup not covered in this class
• Not going into Dockerization / Development installation
• Other clusters: Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), Amazon Elastic Container Service for Kubernetes (Amazon EKS)
• Ansible, Terraform, Puppet or Chef are not in our scope
• Other Loadbalancers: HaProxy, Metallb will not be shown
• Shared persistent data: Longhorn
• Monitoring / Logging / Optimizations are not in our scope

• Name, skillset, expectations

• We will ask each participant (not really a random order) a simple question
• At the end a fully fledged project will be shown

For this guide, you may want to have a minimal Ubuntu LTS installed on all machines. We are using 3 Bare-Metal Servers. You can perform the same deployment on RancherOS, CentOS and any Redhatish OS family in a similar way on any environment.

Public IP(s) and a router / firewall is not optional :)

Coffee and Space, or how Einstein put it: Space-Time. Why ?! For servers of course.

What will you do with a cluster ?

How much time should I invest in learning this sorcery ?

The simplest way to get involved with us is by joining PeakIt 003 Slack channel

Why→