Drupal provides the application behind a content-managed website: editors can create and update material through a web interface instead of changing site code for every page. Modules and themes shape the features and presentation, making it useful when a site's content and publishing needs extend beyond a simple set of static pages. A Kubernetes deployment still needs to preserve the database, uploaded files and the particular extensions that make that site work.
Deployment and operating notes
The recovered chart combined Drupal with a Bitnami MariaDB dependency and very old Kubernetes prerequisites. Drupal’s current upgrade documentation distinguishes major-version upgrades from routine updates and requires checking module, theme and platform compatibility. The retirement of the old chart says nothing by itself about Drupal’s application lifecycle.
Inventory Composer dependencies, custom modules, themes, PHP version, database version and both public and private file storage. Build a reproducible application image and preserve the matching database and files before upgrading. Use a private restored copy to test update hooks, login, content editing, scheduled tasks and file access. Verify that chart image availability and database dependencies meet current publisher terms rather than relying on historical Bitnami defaults. Multi-replica web pods need an intentional shared-file and session design; increasing replicas is not a complete availability plan. Keep a coordinated pre-upgrade restore point because rolling the image back may be unsafe after schema or content transformations.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://new.drupal.org/ and returned HTTP 200 on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Drupal is one of the most versatile open source content management systems on the market.This chart bootstraps a Drupal deployment on a Kubernetes cluster using the Helm package manager.
It also packages the Bitnami MariaDB chart which is required for bootstrapping a MariaDB deployment as a database for the Drupal application.
Prerequisites
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
Why Use Drupal?
INNOVATION
A Platform for digital innovation and ideas
Drupal enables continuous digital innovation at leading organizations like Weather.com and NBCUniversal. With Drupal, marketers and web developers can create and manage great web, mobile and social experiences. And they can improve and adapt quickly thanks to ongoing innovation and ideas from the Drupal community.
SPEED
Build new sites and experiences faster
Speed matters in digital marketing. Digital-first organization needs a platform that helps them move quickly and capitalize on business opportunities. Drupal’s flexible platform lets marketers and developers overcome bottlenecks and delays so they can run a fast and agile team and create amazing experiences.
SCALABILITY
World’s busiest sites run on Drupal
Drupal is enterprise-ready for the world’s busiest websites like GRAMMY.com and The Olympics where failure is not an option. And, more than just supporting high traffic sites, Drupal will scale with your business and your brands for your next-generation digital transformation and allow you to evolve down the road without skipping a beat.
Persistence
The configured image must store Drupal data and Apache configurations in separate paths of the container.
The Bitnami Drupal image stores the Drupal data and Apache configurations at the /bitnami/drupal and /bitnami/apache paths of the container. If you wish to override the image value, and your image stores this data and configurations in different paths, you may specify these paths with volumeMounts.drupal.mountPath and volumeMounts.apache.mountPath.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the Configuration section to configure the PVC or to disable persistence.
- Existing PersistentVolumeClaim
- Create the PersistentVolume
- Create the PersistentVolumeClaim
- Install the chart
Get started with Drupal by downloading it yourself, or work with design shops and developers who can help realize your vision. Drupal’s modular approach and ready-to-go configurations provide rapid time to market and the ability to keep pace with digital evolution.
Sources & further reading
Spotted something that needs another look?
Help improve this page →