Wordpress operator for Kubernetes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Vladimir Smagin 1108107876 fix readme typo 1 viikko sitten
build bootstrap 6 kuukautta sitten
cmd/manager bootstrap 6 kuukautta sitten
deploy readme 1 viikko sitten
pkg add logging to deletion 1 viikko sitten
vendor use vendoring, add jenkins pipeline 2 kuukautta sitten
version add pdb resource 1 viikko sitten
.gitignore bootstrap 6 kuukautta sitten
Dockerfile add pdb resource 1 viikko sitten
Jenkinsfile use vendoring, add jenkins pipeline 2 kuukautta sitten
README.md fix readme typo 1 viikko sitten
VERSION add pdb resource 1 viikko sitten
go.mod use vendoring, add jenkins pipeline 2 kuukautta sitten
go.sum use vendoring, add jenkins pipeline 2 kuukautta sitten
logo.png add logo 6 kuukautta sitten
tools.go bootstrap 6 kuukautta sitten

README.md

Wordpress operator for Kubernetes

Run multiple Wordpress instances in your Kubernetes cluster.

Build sources

Prebuilt images

You can find images here https://hub.docker.com/r/iam21h/wordpress-operator

Deploy operator

kubectl -f deploy/service_account.yaml
kubectl -f deploy/role.yaml
kubectl -f deploy/role_binding.yaml
kubectl -f deploy/operator.yaml

Your first Wordpress deployment

Use internal or external database. Internal database means a single pod with MariaDB without any replication or clusterization, my Wordpress operator is NOT MySQL operator. If you need database high availability use specific MySQL operator to create cluster.

Think scalability before first start, because you can’t mount ReadWriteOnce persistent volume to multiple pods (replicas > 1), so you need storage class with ReadWriteMany feature.

Changed: now PVCs not purging after custom resource deletion. To delete PVCs use special flags.

This sample resource can help you run your first instance with many pods:

apiVersion: blindage.org/v1alpha1
kind: Wordpress
metadata:
  name: my-test-wordpress
spec:
  replicas: 3
  databaseVolumeSize: 1Gi
  wordpressVolumeSize: 2Gi
  # set storage class with ReadWriteMany feature
  wordpressStorageClass: nfs
  # purge PVCs after use
  databaseVolumeCleanup: true
  wordpressVolumeCleanup: true
  podDisruptionBudget:
    maxUnavailable: 1

podDisruptionBudget supports maxUnavailable and minAvailable, rules only Wordpress pods.

Or if you want to use external database and restore from backup:

apiVersion: blindage.org/v1alpha1
kind: Wordpress
metadata:
  name: another
spec:
  importBackup:
    databaseBackupFile: s3://mywpbackup/backup.sql.gz
    wordpressBackupFile:
    bucketRegion:
    bucketAccessKeyID:
    bucketSecretKey:
  database:
    database: wordpress
    hostname: my-test-wordpress-database
    password: wordpress
    username: wordpress
  replicas: 1
  wordpressVolumeSize: 1Gi

Look to pkg/apis/blindage/v1alpha1/wordpress_types.go to find more parameters like affinity or annotations.


Copyright by Vladimir Smagin (21h) 2019
http://blindage.org email: 21h@blindage.org
Project page: https://git.blindage.org/21h/wordpress-operator