HA Kubernetes Autoscaling & Zero-Trust Setup
Budget: $250 – $750 USD
Task doc: https://docs.google.com/document/d/1GZY-GAfx7x3dJIAOK5uacXDMPfXywXfLW_VvzK31izU/edit?tab=t.0#heading=h.mdpldm4tzx7v
TASK DOCUMENT: Enterprise HA Kubernetes Autoscaling + Zero-Trust (Bare-Metal Provider)
1- Objective
1- Deliver an Enterprise-grade, High Availability (HA) Kubernetes cluster on a dedicated bare-metal cloud hosting provider (preferred: Oracle OKE + bare-metal node pools, or equivalent if faster and comparable long-term cost to Scaleway).
2- Phase 1 focuses on proving horizontal autoscaling up/down using two different test Docker apps the developer made for testing, demonstrating multi-workload scaling within the same cluster.
3- Phase 2 onboards the production Docker app and confirms the same autoscaling behavior.
4- Phase 3 completes the cluster to zero-trust security and full enterprise operational standards.
2- Scope (What is included)
Phase 1 — “Autoscaling Proof on Bare-Metal Platform” (primary acceptance gate)
1- Provision/configure OKE (or equivalent managed control plane) with HA worker topology on bare-metal node pools.
2- Implement pod autoscaling and node autoscaling with tunable scale-down behavior, including consolidation/downscale parameters.
3- Deploy two different test Docker apps (created by dev) and demonstrate:
=> App A scales pods up/down under load and stabilizes
=> App B scales pods up/down under a different load profile (different CPU/memory/request patterns)
=> Cluster scales nodes up/down to match demand (not just pods)
4- Produce a video demo + evidence pack showing autoscaling behavior meets “Enterprise HA k8 autoscaling cluster standards.”
Phase 2 — “Production App Onboarding”
1- Deploy the provided production Docker app into the cluster using the same patterns proven in Phase 1.
2- Validate scaling and resilience behavior (same evidence expectations, production-safe).
Phase 3 — “Zero-Trust + Enterprise Hardening”
1- Implement a zero-trust security posture (network, identity, workload, supply chain, and policy enforcement).
2- Implement enterprise observability, upgrade strategy, backup/restore, and runbooks.
3- Deliver full documentation and reproducible infrastructure definition.
3- Out of Scope (explicitly not required in Phase 1)
1- Production app changes/refactors (unless required for basic container health endpoints and safe scaling signals).
2- Advanced multi-region disaster recovery (can be proposed as an optional extension).
3- “Perfect architecture” debates—results first, then refinement.
TASK DOCUMENT: Enterprise HA Kubernetes Autoscaling + Zero-Trust (Bare-Metal Provider)
1- Objective
1- Deliver an Enterprise-grade, High Availability (HA) Kubernetes cluster on a dedicated bare-metal cloud hosting provider (preferred: Oracle OKE + bare-metal node pools, or equivalent if faster and comparable long-term cost to Scaleway).
2- Phase 1 focuses on proving horizontal autoscaling up/down using two different test Docker apps the developer made for testing, demonstrating multi-workload scaling within the same cluster.
3- Phase 2 onboards the production Docker app and confirms the same autoscaling behavior.
4- Phase 3 completes the cluster to zero-trust security and full enterprise operational standards.
2- Scope (What is included)
Phase 1 — “Autoscaling Proof on Bare-Metal Platform” (primary acceptance gate)
1- Provision/configure OKE (or equivalent managed control plane) with HA worker topology on bare-metal node pools.
2- Implement pod autoscaling and node autoscaling with tunable scale-down behavior, including consolidation/downscale parameters.
3- Deploy two different test Docker apps (created by dev) and demonstrate:
=> App A scales pods up/down under load and stabilizes
=> App B scales pods up/down under a different load profile (different CPU/memory/request patterns)
=> Cluster scales nodes up/down to match demand (not just pods)
4- Produce a video demo + evidence pack showing autoscaling behavior meets “Enterprise HA k8 autoscaling cluster standards.”
Phase 2 — “Production App Onboarding”
1- Deploy the provided production Docker app into the cluster using the same patterns proven in Phase 1.
2- Validate scaling and resilience behavior (same evidence expectations, production-safe).
Phase 3 — “Zero-Trust + Enterprise Hardening”
1- Implement a zero-trust security posture (network, identity, workload, supply chain, and policy enforcement).
2- Implement enterprise observability, upgrade strategy, backup/restore, and runbooks.
3- Deliver full documentation and reproducible infrastructure definition.
3- Out of Scope (explicitly not required in Phase 1)
1- Production app changes/refactors (unless required for basic container health endpoints and safe scaling signals).
2- Advanced multi-region disaster recovery (can be proposed as an optional extension).
3- “Perfect architecture” debates—results first, then refinement.