Kubernetes on Random Ramblings

Busy Engineers Guide to Deploying on K8s Part 1 - Setting up Docker with GitHub Packages

Tue, 12 Oct 2021 00:00:00 +0000

Busy Engineers Guide to Deploying on K8s Part 1 - Setting up Docker with GitHub Packages

Post Valid as of October 12, 2021.

Busy Engineer’s Guide to Deploying On K8s

While trying to take some coworkers through setting up Docker with GitHub Packages I ran some not obvious edges and my boss pointed out for new to Docker and new to Kubernetes people these could be totally derailing corners. I have to agree, so this series will take people front to back through setting up Kubernetes with the options most readily available to us.

Busy Engineers Guide to Deploying on K8s Part 2 - Kind

Tue, 12 Oct 2021 01:00:00 +0000

Busy Engineers Guide to Deploying on K8s Part 2 - Kind

Post Valid as of October 12, 2021.

Busy Engineer’s Guide to Deploying On K8s

This is a continuation from the last post in the series. There are three primary ways to run Kubernetes locally on a notebook: Kind, k3d, and Minikube. I personally far prefer k3d due to it having good defaults to get up and running with stateful sets long before the other two and it can create large worker nodes, these have lead to a loyalty to the product. However, my org seems to have standardized on Kind for most of their CI so I will be covering that here as it is the easiest for my coworkers to find help and documentation. It is also an excellent product to get started with Kubernetes.

Busy Engineers Guide to Deploying on K8s Part 3 - Helm

Tue, 12 Oct 2021 02:00:00 +0000

Busy Engineers Guide to Deploying on K8s Part 3 - Helm

Post Valid as of October 12, 2021.

Busy Engineer’s Guide to Deploying On K8s

Ok so now that you have Kubernetes installing in a deployment and you can see it with kubectl port-forward how to you get beyond the toy stage?

Helm Charts

Helm is a great way to make your app “production ready” on Kubernetes with minimal effort assuming you do not try to overthink your deployment. Helm fundamentally provides a way for us to deploy apps to kubernetes by easily changing a handful of values at deployment time or in something called a values.yaml

Random Kubernetes Failures and Node Size

Tue, 09 Mar 2021 00:00:00 +0000

Random Kubernetes Failures and Node Size

I had a report of ingress failing on traefik randomly during a test job and since it worked on a local workstation the belief was it had to be a problem with traefik. I looked at the logs and asked them to spin up bigger nodes for the test and it fixed things.

The reason the beefier machines come into play are varied but ultimately come down to “no free lunch”. It all started with these log entries in traefik:

Getting the DataStax cass-operator working on Mac

Tue, 23 Feb 2021 00:00:00 +0000

Getting the DataStax cass-operator working on Mac

Just leaving this here for anyone coming back to this later. This works as of Feb 23 2021 on Big Sur

install docker desktop https://www.docker.com/products/docker-desktop
install k3d https://github.com/rancher/k3d#get you can just run curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash
create cluster: k3d cluster create
install operator manifest kubectl create -f https://raw.githubusercontent.com/datastax/cass-operator/v1.5.1/docs/user/cass-operator-manifests-v1.19.yaml
download a cassandra data center yaml curl -O https://gist.githubusercontent.com/rsds143/0e9263ed4287d888fab36eb3e4aec502/raw/f919172c64452a2277b7523d680a9e12916d0d39/cassandra-dc.yaml
run kubectl create -f cassandra-dc.yaml --namespace cass-operator
wait for cassandra to come up kubectl logs cluster1-dc1-default-sts-0 --namespace cass-operator server-system-logger
get username export CQLUSER=$(kubectl get secret cluster1-superuser -o json -n cass-operator | grep \"username\" | sed -E 's/\"(.+)\": \"(.+)\"/\2/' | base64 -d)
get password export CQLPASS=$(kubectl get secret cluster1-superuser -o json -n cass-operator | grep \"password\" | sed -E 's/\"(.+)\": \"(.+)\"/\2/' | sed -E 's/,*$//g' | base64 -d )
log into cqlsh kubectl exec -it -n cass-operator cluster1-dc1-default-sts-0 -- cqlsh -u $CQLUSER -p $CQLPASS
enjoy your cassandra cluster

The yaml I have linked too above is here