ASP.NET Core on Kubernetes
ASP.NET Core Web APIs with Entity Framework Core.
larakube dotnet:newdotnet:new starts an ASP.NET Core 9.0 Web API with Microsoft's own template, set up with Entity Framework Core and the services you pick.
dotnet:new creates the app and its Kubernetes manifests, but there's no production image for it yet: it warns No production image template for .NET Core yet and skips the Dockerfile. With no image, larakube up has nothing to run and cloud:deploy has nothing to ship. NestJS is the first framework through this path, and the rest follow one at a time.
🚀 Create a project
larakube dotnet:new api
LaraKube CLI runs dotnet new webapi inside the .NET 9 SDK container, so you don't need the SDK on your machine, then asks:
| Choice | Options | With --fast |
|---|---|---|
| Database (Entity Framework Core) | PostgreSQL (recommended, via Npgsql), MySQL (Pomelo), MariaDB | PostgreSQL |
| Cache | Redis (recommended), Memcached | Redis |
| Object storage | None, MinIO (recommended), SeaweedFS, Garage | MinIO |
| Search | None, Meilisearch, Typesense | None |
🧱 What your app is set up for
| Piece | Detail |
|---|---|
| Runtime | ASP.NET Core 9.0, listening on port 8080 |
| Migrations | dotnet ef database update — set up in the project, not yet run on deploy |
| Health check | /healthz |
🏘️ Plex Commons
.NET apps will join the shared Plex Commons for their database, cache and storage once this scaffolder is verified.