Skip to main content

ALL SYSTEMS OPERATIONAL //PROXMOX & K3S LIVE

Kalash Bijukchhe /Junior Cloud & DevOps Engineer

DECLARATIVE INFRASTRUCTURE.AUTOMATED DELIVERY.

Built with intent. Operated with care.

I turn infrastructure into code and complexity into dependable systems. From AWS to a hands-on Proxmox lab, I build, break, and understand what runs beneath.

Cloud infrastructure × Continuous deliveryScroll to explore

The tools. The systems. The craft.

  • AWS
  • Kubernetes
  • Terraform
  • Docker
  • GitHub Actions
  • Linux
  • ArgoCD

01 / SELECTED ENGINEERING

LESS THEORY.
MORE PROOF.

Three systems. Real constraints.
The architecture, the failures, and the work that made them run.

01 HYBRID CLOUD / MACHINE LEARNING

AI INFERENCE
GITOPS.

A cloud-to-homelab delivery pipeline. Built in GitHub. Stored in AWS. Reconciled in the homelab.

MAX UNAVAILABLE PODS
0
SURGE POD ALLOWED
1

GitHub Actions builds the FastAPI inference proxy into private AWS ECR. ArgoCD reconciles its Helm chart into k3s on Proxmox. A rolling-update policy uses maxUnavailable: 0 and maxSurge: 1; readiness gates traffic on Ollama backend availability.

Kubernetes (k3s)HelmArgoCDGitHub ActionsAWS ECRFastAPIOllamaProxmox
Explore the repository
SYSTEM TOPOLOGY / 01 DELIVERY FLOW
Infrastructure architecture diagramA GitHub Actions build pushes to AWS ECR. ArgoCD reconciles the Helm chart into k3s on Proxmox, where FastAPI connects to Ollama.GitHubAWS ECRArgoCDProxmox / k3sFastAPI + Ollama
Cloud-built. Locally reconciled.
  1. 01GitHubBUILD / PUSH
  2. 02AWS ECRPRIVATE REGISTRY
  3. 03ArgoCDRECONCILE
  4. 04Proxmox / k3sHYBRID RUNTIME
  5. 05FastAPI + OllamaINFERENCE / PROBES
02 STATEFUL APPLICATION / CONTINUOUS DELIVERY

ERP LITE
GITOPS.

From a commit to a running application. Immutable artifacts, persistent data, and a cluster that reconciles itself.

IMMUTABLE IMAGE TAGS
SHA
EXPLICIT BUILD TARGET
AMD64

Docker Buildx produces linux/amd64 images in GitHub Actions, pushes immutable commit-SHA tags to GHCR, and updates Helm values. ArgoCD syncs, prunes, and self-heals a Next.js deployment with PostgreSQL on persistent storage, Traefik ingress, and cert-manager TLS.

Kubernetes (k3s)HelmArgoCDGitHub ActionsGHCRTraefikcert-managerPostgreSQLNext.js
Explore the repository
SYSTEM TOPOLOGY / 02 DELIVERY FLOW
Infrastructure architecture diagramGitHub Actions builds an AMD64 image into GHCR. ArgoCD reconciles the Helm deployment to k3s, with Traefik ingress and PostgreSQL persistent storage.GitHub ActionsGHCRArgoCDNext.js / k3sPostgreSQL
One commit. A reconciled system.
  1. 01GitHub ActionsBUILD LINUX / AMD64
  2. 02GHCRIMMUTABLE SHA
  3. 03ArgoCDSYNC / SELF-HEAL
  4. 04Next.js / k3sTRAEFIK + TLS
  5. 05PostgreSQLPERSISTENT VOLUME
03 AWS / DECLARATIVE INFRASTRUCTURE

SECURE AWS
FOUNDATIONS.

A deliberately small attack surface. Public at the load balancer. Private everywhere that matters.

NETWORK TOPOLOGY
2 AZ
PUBLIC INSTANCE IPs
0

Terraform provisions a VPC across two availability zones, with two public and two private subnets, route tables, an Internet Gateway, and NAT Gateway. A public ALB forwards to a health-checked EC2 Nginx host bootstrapped through user_data.

TerraformAWS VPCALBEC2NAT GatewayIAMSSM Session ManagerNginx
Explore the repository
SYSTEM TOPOLOGY / 03 DELIVERY FLOW
Infrastructure architecture diagramTerraform provisions an AWS VPC across two availability zones. A public application load balancer routes into private EC2, with administrative access through SSM rather than SSH.TerraformAWS VPCPublic ALBPrivate EC2AWS SSM
Public entry. Private infrastructure.
  1. 01TerraformDECLARE / APPLY
  2. 02AWS VPCTWO AVAILABILITY ZONES
  3. 03Public ALBHEALTH-CHECKED
  4. 04Private EC2NGINX / NO PUBLIC IP
  5. 05AWS SSMIAM-BASED ACCESS
END OF SELECTED WORK03 / 03

02 / Behind the infrastructure

Curious by nature.
Engineer by
practice.

I’m Kalash, a Junior Cloud & DevOps Engineer based in Adelaide. My lab is where theory meets the uncomfortable reality of a system that needs fixing. I build, break, investigate, and make the next deployment better.

Currently studying
Master of IT · Class of 2028

Next milestone
Microsoft AZ-104 · In preparation

/01

Declare the intent.

Infrastructure in Terraform. Workloads in Helm. Configuration that can be reviewed, versioned, and reproduced.

/02

Close the loop.

GitHub Actions builds it. ArgoCD reconciles it. Health probes decide when a workload is ready for traffic.

/03

Follow the failure.

From an unhealthy ALB target to a container architecture mismatch: inspect the evidence, isolate the cause, fix the system.

03 / What's next

Good systems start
with a conversation.

Based in Adelaide. Open to junior cloud and DevOps opportunities, and people building things that matter.

kalashbijukchhe74@gmail.com

Let's make the next deployment a good one.