I’m Ulli, yaml Engineer based in Nuremberg, Germany.
Having a DevOps mindset and proficiency in the CNCF landscape are my keys.
Also I am good at
From CI/CD with Gitops patterns to classical DevOps practices, whatever speeds up the development process and is needed by the team.
Cloud is not just someone else's computer. It's the ecosystem alongside the compute instances.
Containers don't solve all the problems, but Kubernetes does.
It all started with a commit to a public github repo. Github workflow picked up this change and triggered a buildjob of the site. It rendered & resolved all node dependencies and packed together a tidy bundle of this page. This package was put in a into a nginx image, which got pushed to the github registry. Now it got picked up by kustomize, which updated the image reference in the kubernetes deployment manifest.
Now ArgoCD got wind of this change and synced it into my kubernetes cluster. Alongside the nginx image with this website, it deployed an Ingress, Service Object and asked for a x509 Certificate from letsencrypt. Kubernetes updated the pods and consolidated the service to point to the new pods. Now you can view it. And all i did, was one commit to a git repo.
Check out this link if you are interested in the always free tier by oracle, running the infrastructure of this webpage.
Oracle provides a generous always free tier, which is sufficiant to run a small Kubernetes Cluster for your homelab. The page you are currently viewing was delivered from that setup to you.
I utilized the fact, that OKE (the kubernetes control plane) is always free and you usually only pay for the worker nodes. Node workers are free, if you use arm64 instances with 200GB of storage. I decided to go with a two node cluster (2CPUs and 12 GB mem each).
On top i deployed cert-manager, argocd, nginx-ingress, longhorn, grafana and dex...
