Tags¶

AI¶

• My Core AI Engineering Persona

AWS¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Pod With AWS Permissions and No Credentials
• A Site That Loads Proves Almost Nothing
• Four Add-ons Between a Bare EKS Cluster and a Working One
• Four Compute Models, One Artifact
• Seventeen Errors, and the Ones That Were Caused by the Fix
• Ten Things That Failed Silently
• The EKS Module Accepted the Setting and Never Sent It
• Two Failures Behind One Load Balancer, and Why Both Components Were Right
• Zero Compute, and Still a Dozen Decisions

AWS KMS¶

• A Site That Loads Proves Almost Nothing
• Zero Compute, and Still a Dozen Decisions

Alpine¶

• The Vulnerability Gate That Blocked Every Build

Amazon EKS¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Pod With AWS Permissions and No Credentials
• Four Add-ons Between a Bare EKS Cluster and a Working One
• Four Compute Models, One Artifact
• Gateway API Three Ways, and What It Actually Buys Over Ingress
• One Chart, a Ladder of Dependencies
• Seventeen Errors, and the Ones That Were Caused by the Fix
• The EKS Module Accepted the Setting and Never Sent It

Amazon S3¶

• A Site That Loads Proves Almost Nothing
• Zero Compute, and Still a Dozen Decisions

Architecture¶

• Four Compute Models, One Artifact
• Gateway API Three Ways, and What It Actually Buys Over Ingress
• One Chart, a Ladder of Dependencies
• Push or Pull: Two Ways to Hand Off a Deployment
• Reading a Helm Chart You Did Not Write
• Ten Things That Failed Silently
• The Jenkinsfile Rewrite Was Mostly Deletions
• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage
• Why I Built My Own CI/CD Stack (And What I Learned)
• Why I Removed Tools from My Container Image (And the Framework I Used to Decide)

ArgoCD¶

• My Builds Were Reproducible, So My Deployments Stopped
• Push or Pull: Two Ways to Hand Off a Deployment
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage

Automation¶

• Building Only What Changed, and the Permissions Ceiling Nobody Warns You About
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image

BuildKit¶

• My Builds Were Reproducible, So My Deployments Stopped
• Trivy Could Not Find the Image I Had Just Built

CI/CD¶

• Building Only What Changed, and the Permissions Ceiling Nobody Warns You About
• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap
• One Pipeline Contract, Three Language Ecosystems
• Push or Pull: Two Ways to Hand Off a Deployment
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• Ten Things That Failed Silently
• The Jenkinsfile Rewrite Was Mostly Deletions
• The Same Pipeline on Two CI Engines: Jenkins and GitHub Actions
• The Vulnerability Gate That Blocked Every Build
• Twelve Fixes to a Pipeline That Was Already Passing

CVE¶

• The Version Override Maven Silently Ignored
• The Vulnerability Gate That Blocked Every Build

Capacity Planning¶

• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready

Career¶

• I Gave Hyperagent One Handle and Nothing Else: It Verified the Rest
• My Core AI Engineering Persona
• Project Card Authoring Standards

CloudFront¶

• A Site That Loads Proves Almost Nothing
• Zero Compute, and Still a Dozen Decisions

Cloudflare¶

• TLS Behind NAT Is Two Problems, Not One

Cloudflare Tunnel¶

• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Comparison¶

• The Same Pipeline on Two CI Engines: Jenkins and GitHub Actions

Configuration¶

• The Ampersand That Silently Truncated My Database URL

Container Security¶

• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• The Vulnerability Gate That Blocked Every Build
• Trivy Could Not Find the Image I Had Just Built

Cost Optimisation¶

• Zero Compute, and Still a Dozen Decisions

DNS¶

• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Databases¶

• The Ampersand That Silently Truncated My Database URL

DebugBox¶

• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide
• Six Things That Break When You Actually Use a Debugging Container
• Why I Removed Tools from My Container Image (And the Framework I Used to Decide)

Debugging¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Site That Loads Proves Almost Nothing
• Building Only What Changed, and the Permissions Ceiling Nobody Warns You About
• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide
• My Builds Were Reproducible, So My Deployments Stopped
• Reading a Helm Chart You Did Not Write
• Seventeen Errors, and the Ones That Were Caused by the Fix
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• Six Things That Break When You Actually Use a Debugging Container
• Ten Things That Failed Silently
• The Ampersand That Silently Truncated My Database URL
• The EKS Module Accepted the Setting and Never Sent It
• Two Failures Behind One Load Balancer, and Why Both Components Were Right

Dependency Management¶

• The Version Override Maven Silently Ignored

DevOps¶

• I Gave Hyperagent One Handle and Nothing Else: It Verified the Rest
• Project Card Authoring Standards

DevOps Toolchain¶

• The Machine I Actually Work From

Docker¶

• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• Building an OCI Image That Boots as a microVM, Not a Container
• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide
• Four Ways to Serve a Frontend, Three of Them Wrong
• My Builds Were Reproducible, So My Deployments Stopped
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• Six Things That Break When You Actually Use a Debugging Container
• The Machine I Actually Work From
• Trivy Could Not Find the Image I Had Just Built
• Why I Removed Tools from My Container Image (And the Framework I Used to Decide)

Dockerfile¶

• Building an OCI Image That Boots as a microVM, Not a Container
• The Machine I Actually Work From

Documentation¶

• I Gave Hyperagent One Handle and Nothing Else: It Verified the Rest
• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap
• Project Card Authoring Standards

ECS Fargate¶

• Four Compute Models, One Artifact

Ephemeral Containers¶

• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide

Gateway API¶

• An ACME Challenge That Could Not Reach Itself
• Four Add-ons Between a Bare EKS Cluster and a Working One
• Gateway API Three Ways, and What It Actually Buys Over Ingress
• Two cert-manager Solvers, and the Flag That Is Off By Default

GitHub Actions¶

• Building Only What Changed, and the Permissions Ceiling Nobody Warns You About
• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap
• Push or Pull: Two Ways to Hand Off a Deployment
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• The Same Pipeline on Two CI Engines: Jenkins and GitHub Actions
• Trivy Could Not Find the Image I Had Just Built
• Twelve Fixes to a Pipeline That Was Already Passing

GitOps¶

• My Builds Were Reproducible, So My Deployments Stopped
• Push or Pull: Two Ways to Hand Off a Deployment
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage

Groovy¶

• Twelve Fixes to a Pipeline That Was Already Passing

Helm¶

• One Chart, a Ladder of Dependencies
• Reading a Helm Chart You Did Not Write

Helmfile¶

• One Chart, a Ladder of Dependencies

IAM¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Pod With AWS Permissions and No Credentials
• Seventeen Errors, and the Ones That Were Caused by the Fix
• The EKS Module Accepted the Setting and Never Sent It

Infrastructure as Code¶

• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl
• Seventeen Errors, and the Ones That Were Caused by the Fix
• The EKS Module Accepted the Setting and Never Sent It
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image

Ingress¶

• Gateway API Three Ways, and What It Actually Buys Over Ingress
• Two cert-manager Solvers, and the Flag That Is Off By Default

Java¶

• One Pipeline Contract, Three Language Ecosystems
• The Version Override Maven Silently Ignored

Jenkins¶

• Building an OCI Image That Boots as a microVM, Not a Container
• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• Release Identity: What a Build Is Called and What Is Allowed to Ship
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• The Jenkinsfile Rewrite Was Mostly Deletions
• The Same Pipeline on Two CI Engines: Jenkins and GitHub Actions
• Twelve Fixes to a Pipeline That Was Already Passing
• Why I Built My Own CI/CD Stack (And What I Learned)

Kubernetes¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Pod With AWS Permissions and No Credentials
• An ACME Challenge That Could Not Reach Itself
• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide
• Four Add-ons Between a Bare EKS Cluster and a Working One
• Four Compute Models, One Artifact
• Gateway API Three Ways, and What It Actually Buys Over Ingress
• My Builds Were Reproducible, So My Deployments Stopped
• One Chart, a Ladder of Dependencies
• Push or Pull: Two Ways to Hand Off a Deployment
• Reading a Helm Chart You Did Not Write
• Six Things That Break When You Actually Use a Debugging Container
• TLS Behind NAT Is Two Problems, Not One
• Ten Things That Failed Silently
• The Machine I Actually Work From
• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage
• Two cert-manager Solvers, and the Flag That Is Off By Default
• Why I Removed Tools from My Container Image (And the Framework I Used to Decide)

Kustomize¶

• Four Compute Models, One Artifact

Lets Encrypt¶

• An ACME Challenge That Could Not Reach Itself
• TLS Behind NAT Is Two Problems, Not One

Load Balancing¶

• Two Failures Behind One Load Balancer, and Why Both Components Were Right

Maven¶

• The Jenkinsfile Rewrite Was Mostly Deletions
• The Version Override Maven Silently Ignored

Microservices¶

• One Chart, a Ladder of Dependencies
• Reading a Helm Chart You Did Not Write

MkDocs¶

• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap

MkDocs Material¶

• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap

Monorepo¶

• Building Only What Changed, and the Permissions Ceiling Nobody Warns You About

NAT¶

• TLS Behind NAT Is Two Problems, Not One
• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Networking¶

• Four Add-ons Between a Bare EKS Cluster and a Working One
• Gateway API Three Ways, and What It Actually Buys Over Ingress
• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Nexus¶

• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• Why I Built My Own CI/CD Stack (And What I Learned)

Nginx¶

• Four Ways to Serve a Frontend, Three of Them Wrong

Node.js¶

• Four Ways to Serve a Frontend, Three of Them Wrong
• One Pipeline Contract, Three Language Ecosystems

OCI¶

• Building an OCI Image That Boots as a microVM, Not a Container
• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl

Observability¶

• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage

Open Source¶

• Choosing the Right Kubernetes Debugging Container: A Variant-by-Variant Guide
• Six Things That Break When You Actually Use a Debugging Container
• Why I Removed Tools from My Container Image (And the Framework I Used to Decide)

Pipeline Design¶

• One Pipeline Contract, Three Language Ecosystems
• The Same Pipeline on Two CI Engines: Jenkins and GitHub Actions
• Twelve Fixes to a Pipeline That Was Already Passing

Platform Engineering¶

• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image
• Why I Built My Own CI/CD Stack (And What I Learned)

PostgreSQL¶

• Six Errors from Building systemd Rootfs Images, and How I Fixed Each

Prometheus¶

• The Monitoring Stack Is the One Thing ArgoCD Does Not Manage

Prompt Engineering¶

• My Core AI Engineering Persona

PyMdown Extensions¶

• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap

Pygments¶

• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap

Python¶

• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap
• One Pipeline Contract, Three Language Ecosystems

React¶

• Four Ways to Serve a Frontend, Three of Them Wrong

Reverse Proxy¶

• Four Ways to Serve a Frontend, Three of Them Wrong

SAST¶

• One Pipeline Contract, Three Language Ecosystems

Security¶

• 401 and 403 Are Different Failures, and One of Them Is Unrecoverable
• A Pod With AWS Permissions and No Credentials
• Zero Compute, and Still a Dozen Decisions

Self-Hosted¶

• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• Why I Built My Own CI/CD Stack (And What I Learned)
• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Serverless¶

• A Pod With AWS Permissions and No Credentials

SonarQube¶

• Building an OCI Image That Boots as a microVM, Not a Container
• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• The Jenkinsfile Rewrite Was Mostly Deletions
• Why I Built My Own CI/CD Stack (And What I Learned)

Spring Boot¶

• The Ampersand That Silently Truncated My Database URL
• The Version Override Maven Silently Ignored
• Two Failures Behind One Load Balancer, and Why Both Components Were Right

Storage¶

• Four Add-ons Between a Bare EKS Cluster and a Working One

Supply Chain¶

• The Version Override Maven Silently Ignored
• The Vulnerability Gate That Blocked Every Build

TLS¶

• An ACME Challenge That Could Not Reach Itself
• TLS Behind NAT Is Two Problems, Not One
• Two Failures Behind One Load Balancer, and Why Both Components Were Right
• Two cert-manager Solvers, and the Flag That Is Off By Default
• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Terraform¶

• Seventeen Errors, and the Ones That Were Caused by the Fix
• Ten Things That Failed Silently
• The EKS Module Accepted the Setting and Never Sent It
• The Machine I Actually Work From

Trivy¶

• Building a Multi-Arch Container CI Pipeline with Hard-Fail Security Gates
• One Pipeline Contract, Three Language Ecosystems
• The Version Override Maven Silently Ignored
• The Vulnerability Gate That Blocked Every Build
• Trivy Could Not Find the Image I Had Just Built

Troubleshooting¶

• An ACME Challenge That Could Not Reach Itself
• Building an OCI Image That Boots as a microVM, Not a Container
• Four Ways to Serve a Frontend, Three of Them Wrong
• MkDocs CI Build Fails, But Locally It Works: The Pygments 2.19 NoneType Trap
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• Six Things That Break When You Actually Use a Debugging Container
• The Vulnerability Gate That Blocked Every Build
• Trivy Could Not Find the Image I Had Just Built
• Twelve Fixes to a Pipeline That Was Already Passing
• Two Failures Behind One Load Balancer, and Why Both Components Were Right
• Two cert-manager Solvers, and the Flag That Is Off By Default
• Your Server Has No Public IP: Serving a Custom Domain with TLS Anyway

Twelve-Factor¶

• The Ampersand That Silently Truncated My Database URL

Verification¶

• A Site That Loads Proves Almost Nothing

Versioning¶

• Release Identity: What a Build Is Called and What Is Allowed to Ship

cert-manager¶

• An ACME Challenge That Could Not Reach Itself
• TLS Behind NAT Is Two Problems, Not One
• Two cert-manager Solvers, and the Flag That Is Off By Default

iximiuz Labs¶

• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image

labctl¶

• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image

microVM¶

• Building an OCI Image That Boots as a microVM, Not a Container
• Four Machines, One Playground: Composing a CI/CD Stack That Boots Ready
• Publishing a Custom Playground on iximiuz Labs: Custom Rootfs, Manifest, and labctl
• The Machine I Actually Work From
• Three Places to Put Provisioning: Init Tasks, Startup Files, or the Image

systemd¶

• Building an OCI Image That Boots as a microVM, Not a Container
• Six Errors from Building systemd Rootfs Images, and How I Fixed Each
• The Machine I Actually Work From