Skip to content

wordpress

This example demonstrates how to use Zarf to deploy a WordPress blog into a cluster.

It is used as a part of the Creating a Zarf Package and Deploying a Zarf Package tutorials.

zarf.yaml

kind: ZarfPackageConfig # ZarfPackageConfig is the package kind for most normal zarf packages
metadata:
name: wordpress # specifies the name of our package and should be unique and unchanging through updates
version: 26.0.0 # (optional) a version we can track as we release updates or publish to a registry
description: | # (optional) a human-readable description of the package that you are creating
A Zarf Package that deploys the WordPress blogging and content management platform
values:
files:
- values.yaml
schema: values.schema.json
components:
- name: wordpress # specifies the name of our component and should be unique and unchanging through updates
description: | # (optional) a human-readable description of the component you are defining
Deploys the Bitnami-packaged WordPress chart into the cluster
required: true # (optional) sets the component as 'required' so that it is always deployed
charts:
- name: wordpress
url: oci://registry-1.docker.io/bitnamicharts/wordpress
version: 26.0.0
namespace: wordpress
valuesFiles:
- wordpress-values.yaml
values:
- sourcePath: ".wordpress.username"
targetPath: ".wordpressUsername"
- sourcePath: ".wordpress.password"
targetPath: ".wordpressPassword"
- sourcePath: ".wordpress.email"
targetPath: ".wordpressEmail"
- sourcePath: ".wordpress.firstName"
targetPath: ".wordpressFirstName"
- sourcePath: ".wordpress.lastName"
targetPath: ".wordpressLastName"
- sourcePath: ".wordpress.blogName"
targetPath: ".wordpressBlogName"
images:
- docker.io/bitnamilegacy/apache-exporter:1.0.10-debian-12-r55
- docker.io/bitnamilegacy/mariadb:12.0.2-debian-12-r0
- docker.io/bitnamilegacy/wordpress:6.8.2-debian-12-r4
manifests:
- name: connect-services
namespace: wordpress
files:
- connect-services.yaml
documentation:
readme: readme.md