Relationship With Productive K3S

productive-k3s-infra and productive-k3s have different responsibilities.

What Productive K3S does

productive-k3s is the cluster bootstrap project. It is responsible for:

• installing k3s
• assembling the selected cluster mode
• installing shared stack components
• validating the resulting stack behavior

What Productive K3S Infra does

productive-k3s-infra prepares the infrastructure context around those bootstrap phases:

• create or target the machines
• derive node roles and service hostnames
• render generated metadata and inventory-like files
• move the productive-k3s bundle into place
• orchestrate the bootstrap sequence across one or more nodes

Shared bootstrap interface

The infrastructure flows in this repository treat the productive-k3s execution modes as the public bootstrap interface:

• single-node
• server
• agent
• stack

Different use cases consume those modes differently:

• multipass: server, agent, stack
• onprem-basic: single-node or server, agent, stack depending on topology
• aws-single-node: operationally one node, but still driven through the shared remote bootstrap layer around productive-k3s

Why the split matters

This separation keeps infrastructure automation replaceable.

You can change:

• how machines are provisioned
• where inventories come from
• which transport is used

without redefining the core cluster bootstrap contract every time.