Epic Goal

• Get proposal approved in upstream Kubernetes for alpha swap support, targeting version 1.22.

Why is this important?

• Many different customer workload scenarios need swap for enablement.
• Upstream issue: https://github.com/kubernetes/kubernetes/issues/53533

Scenarios

1. Long-running applications where initial memory is swapped out
2. Local development/systems with fast storage
3. Low-footprint systems/edge devices
4. Live migration of workloads
5. Memory flexibility?
6. See "Use Cases" in upstream doc: https://docs.google.com/document/d/1CZtRtC8W8FwW_VWQLKP9DW_2H-hcLBcH9KBbukie67M/edit#heading=h.x1v634owxotc

Acceptance Criteria

• Upstream KEP written, approved and merged as "implementable"
• Graduation to alpha in 1.22, per upstream KEP criteria
• Downstream enhancement written, approved, and merged as "implementable"
• Add tech preview MCO/OpenShift support for launching an OpenShift cluster with nodes with swap in 4.9

Dependencies (internal and external)

1. Working with k8s community to agree on a common proposal

Done Checklist

See https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2400-node-swap/README.md#alpha

• CI - CI is running, tests are automated and merged.
• Release Enablement N/A
• DEV - Upstream code and tests merged: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2400-node-swap/README.md#alpha
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - No downstream documentation.