Infrastructure use cases for Productive K3S

Productive K3S Infra

Productive K3S Infra provides pre-assembled infrastructure flows for running Productive K3S on local virtual machines, basic cloud setups, and existing on-premises hosts.

It focuses on provisioning, inventories, networking assumptions, bootstrap orchestration, and validation, while Productive K3S remains the cluster bootstrap layer.

View on GitHub Open README

Why it exists

Option 1

Raw infrastructure scripts are flexible, but inconsistent and hard to reuse.

Option 2

A fully productized platform can be powerful, but too heavy for early adoption and evaluation.

Productive K3S Infra provides the middle path: repeatable infrastructure flows around Productive K3S.

Keep Productive K3S as the bootstrap contract
Package real use cases instead of toy examples
Make local, cloud, and SSH-based validation predictable

Target use cases

  • Local multi-node validation with Multipass
  • Existing hosts reachable over SSH
  • Basic single-node cloud evaluation on AWS
  • Teams that want reusable infrastructure flows before custom hardening

Design principles

  • Use cases first: public entry points are complete deployment flows, not fragments
  • Reuse shared layers: keep provisioning and remote bootstrap logic aligned
  • Stay explicit: node roles, generated metadata, and make targets should be obvious

Supported environments

  • Multipass on a local development machine
  • Existing Ubuntu or Debian hosts reachable over SSH
  • Basic AWS EC2 single-node setups
  • Productive K3S source bundles from a local checkout or a published release

What it is not

  • Not a replacement for Productive K3S
  • Not a managed platform or a hardened production framework
  • Not a promise that every public use case is production-ready as-is

It is the infrastructure companion layer around Productive K3S.