Skip to content
View japplewhite's full-sized avatar
  • Applewhite IT Consulting LLC
  • United States

Block or report japplewhite

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

Jeff Applewhite

Infrastructure engineer and consultant — Applewhite IT Consulting, LLC, New River Valley, Virginia.

I work on the layer underneath applications: Linux, Kubernetes, networking, storage, and AI/GPU infrastructure. What's here is working code from real engagements, plus labs where I rebuild things from scratch to stay fluent in the parts managed services normally hide.

applewhiteit.com · Field Notes · Contact


Projects

ansible-collection-omada — Ansible collection for TP-Link Omada SDN, published on Ansible Galaxy. Written during a forklift network upgrade so VLANs, networks, and port configuration live in version control instead of a controller GUI.

tplink-omada-api-fork — Working fork of the upstream Python client, adding LAN/VLAN and port-label read and write support the original didn't expose. This is where the API TP-Link never documented got mapped.

akamai-k8s-lab — A four-node Kubernetes cluster built with kubeadm on plain Linux VMs, deliberately configured without cloud primitives: no managed control plane, no cloud controller manager, no cloud load balancer, no cloud CSI. Includes the project plan, stage-by-stage runbooks, manifests, and break/fix evidence.

llm-serving-lab — Self-hosted model serving on rented GPUs: what it costs, what breaks, and what's actually worth running yourself.

Upstream

Reported a reproducible containerd defect where one tool pulled an image successfully while the path Kubernetes actually uses failed on the same machine, against the same registry, with the same certificate. Posted the full reproduction, the diagnostic sequence, and the workaround, confirming the bug on a version later than the original report.

Writing

Build logs rather than tutorials, at applewhiteit.com/blog:

Working together

Available for project, contract, and fractional engagements — Linux, Windows, macOS, networking, Kubernetes, cloud, storage, SRE, and AI/GPU infrastructure.

📫 applewhiteit.com/contact

Pinned Loading

  1. ansible-collection-omada ansible-collection-omada Public

    Ansible collection for TP-Link Omada SDN network automation

    Python 1

  2. llm-serving-lab llm-serving-lab Public

    Self-hosted LLM serving on rented GPUs — what it costs, what breaks, and what's worth running yourself

    Shell

  3. tplink-omada-api-fork tplink-omada-api-fork Public

    Working fork of MarkGodwin/tplink-omada-api - adds LAN network/VLAN and port-label read+write support

    Python

  4. akamai-k8s-lab akamai-k8s-lab Public

    Four-node Kubernetes cluster built with kubeadm on plain Linux VMs — no managed control plane, no cloud load balancer, no cloud CSI

    Shell