Skip to content
View kogeler's full-sized avatar

Block or report kogeler

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.

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
kogeler/README.md

About

I work on infrastructure and platform engineering, mostly around Linux, Kubernetes, networking, observability, storage, and distributed systems. A significant part of my experience comes from operating blockchain infrastructure, although the underlying work is generally applicable to other stateful and distributed platforms.

My background includes bare-metal systems, data-centre and telecommunications environments, Linux networking, and troubleshooting across both software and hardware layers. I have worked with physical servers, storage and network devices, virtualization, containers, proxies, databases, and Kubernetes clusters in self-hosted and cloud environments. I am comfortable working below the orchestration layer when a problem requires looking at operating-system behaviour, processes, memory, disks, network traffic, or hardware characteristics.

I mostly use Ansible, Terraform, Helm, and container tooling to keep infrastructure reproducible and understandable. I also write operational services and automation in Python and Go. I apply software testing and QA practices to infrastructure work, including automated validation, isolated test environments, regression tests, CI checks, deployment gates, and verification of upgrade, migration, and failure scenarios.

Much of this work involves investigating problems that do not belong to a single component and tracing them through application, protocol, operating-system, network, storage, or infrastructure layers. When fixing such problems, I try to leave behind a reproducible test or automated check that prevents the same failure from being introduced again.

Most of my production work is in private or employer-owned repositories. The public repositories and contributions linked below are selected examples rather than a complete work history.

Pinned Loading

  1. substrate-cross-compiler-env substrate-cross-compiler-env Public

    Shell 4 2

  2. tooling tooling Public

    Python

  3. k8s-lab k8s-lab Public

    Reusable building blocks for a single-host Kubernetes laboratory on Debian-family Linux: LXC/LXD nodes driven by Cluster API (CAPN), Ansible roles, a Terraform module, and Helm charts (Calico, Meta…

    HCL 1

  4. mini-pig-ansible-collection mini-pig-ansible-collection Public

    Ansible collection for a self-hosted, bare-metal Debian/Ubuntu stack — anti-censorship proxies, VPN, firewall, monitoring, and host bootstrap.

    Jinja