Drupal on Kubernetes
Running Drupal on Kubernetes: stateless PHP containers, shared file storage or object storage, database and cache services, cron as jobs and rolling deploys with database updates and configuration import.

Infrastructure choices for self-hosted Drupal: web server and database, containers and Kubernetes, cloud and on-premises hosting, multisite layouts and Composer-based build and release.
Running Drupal on Kubernetes: stateless PHP containers, shared file storage or object storage, database and cache services, cron as jobs and rolling deploys with database updates and configuration import.
Packaging a Composer-built Drupal codebase into images, separating code from files and settings, environment-specific settings.php includes and image rebuilds for security releases.
Self-managed Drupal on AWS: compute options, managed MySQL or PostgreSQL, S3 for files through s3fs, CloudFront caching with cache tag purging and backup design.
Running Drupal on Azure: app hosting choices, Azure Database for MySQL or PostgreSQL, Blob storage for files, Entra ID sign-in and private networking.
Hosting Drupal inside a private data center or a network without internet access: Composer package mirrors, update status checks that cannot reach Drupal.org, and patching discipline.
Serving Drupal from Nginx instead of Apache: recreating protections that .htaccess gives Apache sites, PHP-FPM pool sizing, clean URLs, private file paths and headers that must pass through.
The database decision for a Drupal platform: version minimums by Drupal release, contributed modules with MySQL-specific code, PostgreSQL's pg_trgm requirement and managed database options.
Serving many independent sites from one codebase with core multisite: separate databases and files, shared upgrades, the risk of coupled release cycles, and when Domain Access or separate codebases fit better.
Managing settings.php across development, staging and production: secrets outside the repository, trusted_host_patterns per environment, file paths and environment-specific configuration splits.
Estimating servers for a Drupal site: anonymous versus authenticated traffic, cache hit rates, PHP memory, database size and search servers, and what load testing should prove before launch.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.