Skip to content
View ffworker's full-sized avatar

Block or report ffworker

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ffworker/README.md

Dennis Kappel

System Administrator · Linux · Infrastructure · Networking

I like knowing why a system works — and why it stopped working.

CV · Self-assessed skills · Repositories


What I work with

Linux · Bash · Docker / Compose · Proxmox · Networking · NetBird / VPN · Kubernetes / k3s · GitHub Actions · NFS / SMB · Prometheus / Grafana

I work best when I can understand the whole path: host → network → service → user. I use documentation, search and AI where they make me faster, but I don't treat generated output as understanding. If I can't reason about a change yet, it belongs in a lab first.

Selected work

Kubernetes break/fix training against real cluster state. Disposable infrastructure, repeatable failure scenarios and live validation.

Kubernetes · Terraform · Ansible · Troubleshooting

A disposable Proxmox lab built around repeatability, teardown boundaries and recovery rather than one-off manual setup.

Proxmox · OpenTofu · Ansible · Cloud-Init

Documentation pipeline that keeps public engineering docs separate from private operational source-of-truth while still validating and delivering them automatically.

Docs-as-code · CI · GitHub Actions · Delivery

The portfolio itself: bilingual static site, explicit technical evidence and a GitOps promotion path to the live CV.

HTML/CSS · GitHub Actions · GitOps · Argo CD

How I work

  • Understand before automating. I want to know what the system is doing before I hide it behind tooling.
  • Use the right tool, not every tool. Manual work is fine when automation would add more complexity than value.
  • Know the boundary. I am comfortable saying when I need documentation, a sandbox, or a second look.
  • Keep recovery boring. Backups, known-good state, rollback paths and useful documentation matter more than cleverness.

Evidence, not badges

CKA validation · Proxmox/IaC validation · Docs CI · Docs delivery


More detail without the usual CV skill inflation: self-assessed skills →

Pinned Loading

  1. my-digital-cv my-digital-cv Public

    Bilingual digital CV and technical portfolio with evidence-backed projects, validated CI, and GitOps delivery.

    HTML

  2. bytegeist-docs bytegeist-docs Public

    documentation of bytegeist

    Python

  3. cka-lab cka-lab Public

    Practical-first CKA training on disposable Proxmox Kubernetes: Terraform, Ansible, break/fix missions, live-state validation, and local progression.

    Python 1

  4. proxmox-lab proxmox-lab Public

    Disposable Proxmox lab factory using Terraform/OpenTofu, Ansible and Cloud-Init.

    HCL