- Published on
Take an ASP.NET Core Web API from a Dockerfile to a running Kubernetes deployment - multi-stage image build, pushing to a registry, and a Deployment plus Service manifest with three replicas behind a load balancer.
Docker
All Posts
- net (41)
- csharp (40)
- entity-framework (18)
- aspnetcore (15)
- efcore (11)
- aspnet-core (11)
- performance (8)
- authentication (4)
- sql-server (4)
- identity (4)
- minimal-api (4)
- design-patterns (3)
- database (3)
- bulk-operations (3)
- ci-cd (3)
- security (2)
- repository-pattern (2)
- sql (2)
docker (2)
- deployment (2)
- angular (2)
- jwt (2)
- migrations (2)
- mediatr (2)
- clean-architecture (2)
- background-jobs (2)
- azure-devops (2)
- pipelines (2)
- devops (2)
- ioc (1)
- api-key (1)
- auditing (1)
- dapper (1)
- dotnet (1)
- decorator (1)
- dependency-injection (1)
- kubernetes (1)
- docker-compose (1)
- react (1)
- signalr (1)
- real-time (1)
- dotnet10 (1)
- scripting (1)
- dotnet-10 (1)
- scaffold (1)
- inheritance (1)
- github-actions (1)
- azure (1)
- concurrency (1)
- middleware (1)
- error-handling (1)
- builder-pattern (1)
- fluentvalidation (1)
- pdf (1)
- questpdf (1)
- reporting (1)
- hangfire (1)
- email (1)
- smtp (1)
- iis (1)
- minimal-apis (1)
- testing (1)
- unit-testing (1)
- xunit (1)
- moq (1)
- multi-tenancy (1)
- quartz (1)
- worker-service (1)
- refit (1)
- httpclient (1)
- api (1)
- authorization (1)
- Published on
One `docker compose up` that brings up a .NET Web API, a React front end, and SQL Server - wired together by service name, with a health check so the API waits for the database to be ready.