Install

Prerequisites

• Kubernetes 1.19+
• Helm 3.8+ (OCI registry support)
• PV provisioner support in the underlying infrastructure (if persistence is enabled)

Install the chart

The chart is published to an OCI registry. Helm installs from it directly; there is no helm repo add step:

helm install my-wordpress oci://ghcr.io/ioanalytica/charts/wordpress-nginx

Or install from local source. The common subchart is not checked in, so fetch it first:

helm dependency build ./chart
helm install my-wordpress ./chart

Without further values the release runs WordPress with a MariaDB server of its own, behind a Service of type LoadBalancer and without an Ingress; passwords that are not set are generated and kept in the release's Secret. A first values file usually sets the administrator and the host name, and with an Ingress in front the Service no longer needs an address of its own:

wordpressUsername: admin
wordpressEmail: admin@example.com

ingress:
  enabled: true
  hostname: blog.example.com

service:
  type: ClusterIP

helm install my-wordpress oci://ghcr.io/ioanalytica/charts/wordpress-nginx -f values.yaml

Pin a version

helm install without --version installs the newest chart version. For production, pin one of the released versions:

helm install my-wordpress oci://ghcr.io/ioanalytica/charts/wordpress-nginx --version <version> -f values.yaml

The chart version names the WordPress release and the chart's build on it; Versioning explains the scheme, and the Changelog lists the versions.

Next steps

• Configuration: WordPress settings, resources and persistence.
• Ingress and redirects: ingress classes, TLS, alias and retired domains.
• Security overview: what is on by default and what is opt-in.
• Coming from the Bitnami chart: what differs for an existing values file.