My road to self hosted kubernetes with k3s

this is a farytale from a devops engineer from Berlin

March 27, 2021 Read
Contribute to This Blog

in this blog post i ll show you how you can create a PR to edit contents of this blog

November 7, 2020 Read
Golang securing rest api with jwts tokens

in this tutorial we ll create a server/client the client generates a token and queries the server with that token and the server checks if that token is valid via a middleware function

November 1, 2020 Read
Golang simple rest api

a very simple rest api that reacts onto different methods (GET/POST) we ll be using gorilla/mux as a router

November 1, 2020 Read
Golang - getting started

introduction on how to run a simple hello world in go

October 31, 2020 Read
Helm3 Getting Started

helm version 3 installation is quiet easy as it can be found in most repositories for me I used sudo pacman -S helm helm version initialize the stable repo to my understanding the helm organization wants to get away from the stable repo being considererd the main source, this is why they ship helm with no default repo enabled. we can enable a repo like this: loeken@0x00E ~ helm repo add stable https://kubernetes-charts.

September 15, 2020 Read
Kubernetes Cert Manager for Letsencrypt Based Certificates With Nginx Ingress

Cert Manager cert manager stores certificates in kubernetes secret store and we can configure the nginx-ingress to use these certificates. cert-manager.yaml wget https://github.com/jetstack/cert-manager/releases/download/v0.15.1/cert-manager.yaml kubectl apply --validate=false -f cert-manager.yaml cert-manager.crds.yaml wget https://github.com/jetstack/cert-manager/releases/download/v0.15.1/cert-manager.crds.yaml kubectl apply --validate=false -f cert-manager.crds.yaml using the ClusterIssuer allows us to create certificates across all namespaces letsencrypt-issuer.yaml apiVersion: cert-manager.io/v1alpha2 kind: ClusterIssuer metadata: name: letsencrypt-prod spec: acme: # The ACME server URL server: https://acme-v02.api.letsencrypt.org/directory # Email address used for ACME registration email: loeken@internetz.

June 13, 2020 Read
Kubernetes Create Images in Google Container Registry

create a user and a project we ll be using the command line tool pacaur -S google-cloud-sdk create a GCP service account; format of account is email address SA_EMAIL=$(gcloud iam service-accounts --format='value(email)' create k8s-gcr-auth-ro) create the json key file and associate it with the service account and save it in k8s-gcr-auth-ro.json gcloud iam service-accounts keys create k8s-gcr-auth-ro.json --iam-account=$SA_EMAIL get the project id PROJECT=$(gcloud config list core/project --format='value(core.project)') add the IAM policy binding for the defined project and service account

June 12, 2020 Read
Kubernetes Prometheus & Grafana

Kubernetes & Prometheus Prometheus by defaults pulls info from the hosts via an http endpoint by default this is the /metrics endpoint Data exposed on this /metrics endpoint needs to support the prometheus endpoint. Exporter is a standalone tool that gathers data and exposes it on the /metrics endpoint These exporters are also available via docker ( can be used as sidecar containers ) Promotheus Server Data Retrieval Worker ( pulls metrics data) Time Series Database ( stores time series metrics data ) Api ( to access this stored data ) View Data Prometheus Web Ui Grafana Terms Targets: anything monitored Units: a subset of whats monitored

June 11, 2020 Read
Kubernetes Nodejs Postgresql Example With Nginx Ingress

Kubernetes nodejs postgresl example with nginx ingress .flex { display: flex; justify-content: center; align-items: center; } Download Image Markup this would be an example to create an ingress that points to our internal node service apiVersion: v1 kind: Ingress metadata: name: node-ingress spec: rules: - host: nodeexample.com http: paths: - test: serviceName: node-service servicePort: 1337 Let’s now combine this with our last two node and postgres deployments we wrote and create a new deployment for node/postgresql using the ingress with an internal service vs using the external service for the node app.

June 10, 2020 Read
Kubernetes Namespaces

Kubernetes namespaces Imagine two teams build similar apps running in the same cluster. in order to avoid duplicated names etc and in order to group resources namespaces can be used to logically separate things. You could also use it to separate staging/production You could also use it if you want to run multiple different production environments. Notes: ConfigMap and Secrets can only be used inside a namespace Namespaces can be used to limit access to namespaces Namespaces can be used to limit resources to namespaces ( cpu / mem / storage ) the default namespaces kubectl get namespaces NAME STATUS AGE default Active 5d14h kube-system Active 5d14h kube-public Active 5d14h kube-node-lease Active 5d14h kubernetes-dashboard Active 5d14h manage namespaces via command line kubectl create namespace mynamespace namespace/mynamespace created kubectl get namespaces NAME STATUS AGE default Active 5d14h kube-system Active 5d14h kube-public Active 5d14h kube-node-lease Active 5d14h kubernetes-dashboard Active 5d14h mynamespace Active 6s kubectl delete namespace mynamespace namespace "mynamespace" deleted to use namespaces in yaml markup simply add:

June 10, 2020 Read
Kubernetes Nodejs Postgresql Example

Deployment example with nodejs / postgresql .flex { display: flex; justify-content: center; align-items: center; } Download Image Markup In this demo example we’ll be deploying the app from the previous docker example which consists of one node and one postgresql container. In the docker example we used a hardcoded username/password combination - which is bad practise: this time we ll be working cleaner by moving the username/password for PG into environmental variables We are going to create a deployment that uses a Secret and a ConfigMap to define values for these 2 environmental variables.

June 9, 2020 Read