Deploying Typo3 on Kubernetes with visual template and KubeKanvas

Deploy a high-availability TYPO3 CMS stack backed by MariaDB, Redis, and an automated Horizontal Pod Autoscaler. This setup configures persistent file storage, session caching, and NGINX Ingress routing for scalable content management workloads.

What's Included

Architecture Overview

External HTTP requests pass through the NGINX Ingress controller to the typo3-service LoadBalancer, which distributes traffic across active typo3-app pods. The TYPO3 application workers read and write persistent media assets to typo3-files-pvc mounted at /var/www/html/fileadmin. Database operations route internally to the typo3-db StatefulSet over db-service:3306, authenticated via typo3-secrets. Session data and application cache operations query the redis StatefulSet via redis-service:6379. The typo3-hpa continuously tracks CPU metrics and dynamically scales web worker replicas based on load.

Prerequisites

• Kubernetes cluster with NGINX Ingress Controller installed
• Metrics Server running on the cluster to enable HPA functionality
• KubeKanvas CLI installed and running on your computer (Optional, if you want to use one-click deployment)

How to Deploy

1. Update the base64 values inside the typo3-secrets manifest with secure credentials for db-password, db-user, and db-name.
2. Configure your domain DNS or local hosts file to point to your NGINX Ingress Controller IP address for root path / routing.
3. Deploy the template to your cluster via kubekanvas the Play button in the top right bar. If you prefer to deploy manually, download the YAML and apply it with kubectl.
4. Wait for all pods to reach Running status. You can monitor progress in the Release Monitor screen.

How to Test

1. Run kubectl get pods -n typo3-project to verify that MariaDB, Redis, and TYPO3 pods show 1/1 or 2/2 in the Ready column.
2. Run kubectl get hpa typo3-hpa -n typo3-project to confirm that current CPU utilization metrics are actively being reported by Metrics Server.
3. Open your browser and navigate to your Ingress IP or configured domain to access the TYPO3 setup and admin login screen.

Use Cases

• High-Traffic Web Publishing: Automatically handles traffic bursts by scaling TYPO3 pods dynamically up to 5 replicas based on CPU demand.
• Persistent Content Management: Preserves user uploads, media libraries, and system files across pod lifecycle events using dedicated PVC mounts.
• In-Memory Caching Acceleration: Offloads frequent database reads and PHP session storage to a high-speed Redis caching tier.

Summary

This template provisions a fully isolated, auto-scaling TYPO3 CMS stack on Kubernetes complete with MariaDB storage, Redis caching, PVC persistence, and NGINX Ingress routing.