Laravel on Kubernetes
The framework LaraKube CLI was built around.
larakube newLaraKube CLI started as a way to run Laravel on Kubernetes, and it's still the deepest path here: pick the server, the queue and realtime features, the frontend and the services, and one command gives you the app, its production image and its Kubernetes manifests.
Laravel was working end to end. Enough has changed around it that it's being re-checked rather than assumed — try it, and expect this badge to turn green once the re-check is done.
🚀 Create a project
larakube new shop
The wizard walks through each part of the stack. --fast takes LaraKube CLI's defaults for all of them.
| Choice | Options |
|---|---|
| Server | FrankenPHP, Nginx (PHP-FPM), Apache (PHP-FPM) |
| Laravel features | Task scheduling, queues, Horizon, Reverb, Scout, Octane, SSR, AI, MCP, Boost, Meet |
| Frontend stack | Livewire, React, Vue, Svelte |
| PHP version and OS | Pick the version and the base image's operating system |
| Database | PostgreSQL, MySQL, MariaDB, SQLite |
| Cache | Redis, Memcached, Database |
| Object storage | SeaweedFS, MinIO, Garage |
| Search (for Scout) | Meilisearch, Typesense, Database |
| Package manager | For your JavaScript assets |
| GitHub Actions | Generate the deploy workflow now, or later |
Want a head start? Blueprints are ready-made larakube new recipes for common app shapes.
🧱 What LaraKube CLI adds
| File | What it does |
|---|---|
Dockerfile.php | The production image on serversideup/php, with assets built inside the image |
.infrastructure/ | Kubernetes manifests: web pods plus a pod per feature you picked (Horizon, queues, Reverb, the scheduler) |
.larakube.json | The project blueprint every later command reads |
.env | Connection values for your services, kept in sync as you add or remove them |
Laravel's own /up route is the health check, and larakube art runs Artisan inside the cluster.
🏘️ Shared services from the Plex Commons
Once the project exists, new joins the cluster's Plex Commons: instead of running its own database and Redis, your app gets its own database, login, Redis slot and bucket on shared services. Pass --no-plex to keep your own pods.
💻 Run it locally
cd shop
larakube up
Your code is mounted into the pods, so edits show up immediately; the first-app walkthrough goes step by step.
☁️ Deploy
larakube env production
larakube cloud:deploy production
➡️ Next
- Cluster Tools and your apps — how your app sits beside the ready-made tools on the same cluster.
- All frameworks — the other stacks LaraKube CLI scaffolds.