Skip to content

Deploy an App from the Marketplace

The App Catalog deploys curated Helm charts and plain-manifest app stacks onto an already-Active Kubernetes cluster — one click instead of hand-writing values.yaml.

Quick steps

  1. ☸ Kubernetes → 🛍️ App Catalog (or from a specific cluster's row).
  2. Pick a stack — categories include AI/ML, Databases, Monitoring, Dev Tools, Storage, and Productivity. Examples from the built-in catalog:
  3. Ollama + Open WebUI — local LLM runtime with a ChatGPT-style web UI (CPU inference; slow above ~7B params).
  4. Qdrant — vector database for RAG/semantic search.
  5. Jupyter + PyTorch, ComfyUI, vLLM — notebook and inference stacks (CPU images; MFCloud doesn't yet schedule K8s pods onto GPU nodes, so GPU-flagged stacks like vLLM will be slow).
  6. Grafana, PostgreSQL, Redis, MinIO, Gitea, n8n, Uptime Kuma, Vaultwarden, code-server, Portainer.
  7. Choose the target cluster and, if the stack exposes any (e.g. Ollama's "model to pull on boot", vLLM's HuggingFace model id, Qdrant's optional API key), fill in the stack's override fields.
  8. Deploy. This runs helm install (Helm-backed stacks) or kubectl apply (plain-manifest stacks) against the cluster and creates a namespace scoped to the release.
  9. Watch progress under 🛍️ Deployed Apps on the cluster's page, or open the deployment's events for the raw log.

Getting in after it deploys

Each deployment row shows an access URL (via the cluster's LoadBalancer/MetalLB, if configured) and, for stacks that generate one, an access token — read the specific stack's access hint on its catalog card:

  • Grafana — log in as admin, password = the generated access token.
  • PostgreSQL — connect as postgres, password = the generated access token.
  • MinIO — console login admin / generated token; S3 API on port 9000.
  • Gitea, n8n, Uptime Kuma — first visit walks you through creating the admin/owner account (no pre-seeded credentials).
  • Vaultwarden, ComfyUI — no built-in login — keep these off any externally-reachable LoadBalancer pool.

Removing a deployment

Deployed Apps table → the deployment's row → Remove. This runs helm uninstall / kubectl delete and drops the namespace.

Custom stacks

Admins can add their own catalog entries (+ New Stack in the App Catalog) pointing at any Helm chart or a generic single-container manifest template — no code change or MFCloud redeploy required; new entries are just rows in the catalog.

See also