mpy-metapackage¶
mpy-metapackage (m2p) is a Helm package designed to deploy a wide range of (Docker)
applications on Kubernetes using Muppy. It is installed by default in every Kubernetes cluster
Muppy installs, and carries all the logic needed to drive an application from the Muppy GUI —
network and security are configured in a few clicks from the Release's Network tab.
Rather than packaging one application, m2p deploys a set of parts you describe in a YAML
blob called the Parts Config (mpy_meta_config), and lets you control them from Muppy.
Four kinds of part:
| Type | Backed by | Purpose |
|---|---|---|
server |
Deployment | exposes HTTP entry points |
worker |
Deployment | background processing, no network entry point |
cronjob |
CronJob | scheduled jobs |
http |
routes only | expose an existing workload (see mpy-Traefik-Dashboard-Ingress) |
m2p benefits from Muppy's Kubernetes setup: ingress routing, network filtering, debug mode and dashboards. It can be used directly or as a sub-chart.
Full documentation¶
m2p has its own documentation site, and it is the authoritative one:
→ https://cmorisse.gitlab.io/mpy-metapackage/¶
This page is deliberately kept short: keeping a second copy of the reference here would drift from the chart it documents. Everything about how m2p works lives with the chart.