In this series, we will be testing out several features in Istio with a local Kubernetes (k3s) cluster. Deploy k3s cluster First step is to deploy the k8s cluster with k3d - a wrapper to run k3s in docker. Start by creating a k3d config file: # k3d-istio.yaml apiVersion: k3d.io/v1alpha2 kind: Simple name: istio servers: 1 agents: 2 ports: # for exposing Istio ingress on localhost - port: 8080:80 nodeFilters: - loadbalancer - port: 8443:443 nodeFilters: - loadbalancer options: k3s: extraServerArgs: - --no-deploy=traefik # we will be using Istio ingress instead Deploy the cluster with k3d

In this article, I will be using the process of building a house as an example to explain how Kubernetes Custom Resources work. Imagine building a custom home, which is a highly detailed and laborious work, that you decided to just hire a home builder. The builder gives you a form to fill out details such as: how many rooms do you need and what size should they be?

Intro I have a side hobby where I try to create minimal container images. There are a number of reasons for this, but the primary one is because I’m a complete geek. Other reasons include: It’s a neatness thing There’s an engineering imperative in me to be minimalist I don’t like waste The process of creation helps me understand the technology a little better Smaller images are great for testing at scale Why The why I do this is mainly because it’s a hobby, but in this case, I started the ultra minimal container image build because someone I work with wanted to build a container for testing Istio latency at scale.

I have had basic experience playing with Terraform to instantiate resources in Kubernetes and AWS, but my previous attempts left me with a thought, how do I implement this at work and scale it up to the team? Terraform creates a local state file which seems like a pain to share around a team. This is when I found out about remote backends. And this is my attempt to learn Terraform S3 backend.