Show newer

My main go to for super speedy local dev testing on k8s: Kind

Fourth NUC arrived. Now I am waiting for the Network Adapter to have a redundant Internet Setup and connect it to my K3S Cluster for a second ETH Validator. Will switch from having 3 NUCs per Validator to 2 with 2 Replicas per Node and some Affinity Rules. The third felt overkill as the Cluster seems rock solid and incase of a broken NUC they are automatically assigned to fallback on having 2 validators running on one of the Nodes, so there will always be 2 Nodes running both validators.

and with all of these new practices and methodologies came new tools and technologies to support them. When companies create job postings for DevOps Engineers, they mostly want operations people who understand these new tools. Mostly an Automation Engineer.

But, Automation is part of the DevOps philosophy but it’s only one piece. Adopting automation without changing your culture to a DevOps mindset of trust, transparency, and fast feedback loops, it’s still just implementing Automation.

Part of the confusion is because a lot of practices came together all at once to form the DevOps movement back in 2009. The culture change was at the centre of the movement. You had influences from Lean Manufacturing, Agile Development and Planning, Continuous Integration and Continuous Delivery, Test-Driven Development, Behavior Driven Development, Cloud Native Microservice Architecture, Infrastructure as Code, Immutable Runtimes, etc.,

It is the practice of development and operations engineers working together during the entire software lifecycle, hopefully on the same team, following lean and agile principles that allow them to deliver high-quality software stably and continuously. It starts with learning how to work differently and embraces cross-functional teams with openness, transparency, and trust as pillars.

The reality is that DevOps is not a job title. It is not something one person does or a team does. It is a cultural transformation on an organizational scale.

I have found that the DevOps Engineer job title is almost always a pure Ops position with no Dev.

DevOps Engineer seems to be a job title that causes a fair amount of confusion. Perhaps this is because it’s an anti-pattern.

CTF Events should be made with a more modern infrastructure approach to make it more challenging. So far I am not keen on joining any more CTF Events that involve Linux or Windows Boxes. The process is getting too similar over time: Port Scan, metasploit, reverse shell, Web Stuff and Linux / Windows enumeration. Looking for Cloud / Edge themed challenges.

I will be participating in KubeCon again this year. Excited to talk with some of my colleagues, even if it will be happening remotely this year. I will also be joining the GitOpsCon and the SPIFFE + SPIRE event. Focus topics for me are: Running Big Data on Kubernetes, Zero Trust Security and IoT / Edge Computing.

Achieved Expert Status at HacktheBox and signed up for the Kubernetes Security Specialist Certification. Should be easy.

PFSense still loses the default Gateway on my CARP Setup in Version 21.1.5. Will have to insert it manually going forward as it's too error prone :(

Fargate has many advantages on EKS if you leave out the cost factor, but for Kube-System Components I would rather prefer an EC2 Node. Especially the missing Daemonset functionality and Metric Components not being really suitable for Fargate prevents it from being a fully fledged Solution. You just wanna use Fargate? You need to have your whole K8s Stack including Elasticsearch in AWS. the integrated Fluent-Bit misses alot of Stuff compared to a Prometheus / Metric-server Solution.

Currently have 100 Percent Upkeep on my Cloud Ethereum 2 Validators. Running on Kubernetes with load balancing and automatic disaster recovery (HA is too expensive). Survived a Migration to new SSDs and from Raspberry PI to NUCs without downtime. Spent a lot of time hardening my OVirt Cluster and K8s which survived even the harshest CIS Benchmarks.

Tried Awesome Tool to clone the remote k8s Cluster to Docker and work on it locally.

Mastodon seems to fit my requirements for a self deployed blogging application. Open-Source, interesting and secure content, fast. Will use it as my main blog.

Migrated my private Kube Cluster from RKE to K3S today. Way more lightweight.

Deployment von Mastodon auf meinem selbst gehosteten Kubernetes Cluster erfolgreich durchgeführt! Link zu dem Compose File findest du auf meinem Github:


Welcome to my Blog! I mostly talk about DevOps, Cloud, Linux and Kubernetes. Huge Tech, Chess and Outdoor Fan.