Wordpress, uses official Docker Wordpress image by default
Wordpress k8s charm
A Juju charm for a Kubernetes deployment of Wordpress, using the official Dockerhub Wordpress image or an image built from this base.
This is a k8s charm and can only be deployed to to a Juju k8s cloud,
attached to a controller using
The image to spin up is specified in the
image charm configuration
option using standard docker notation (eg. 'localhost:32000/mywork-rev42').
The default image is Dockerhub's
wordpress:php7.3 image, but you can also
use private images by specifying
Configuration for the Wordpress image is in standard Juju config. In particular:
db_password. This charm may in future be relatable to a MySQL deployment, when the MySQL charm is updated to support cross model relations.
ports. Custom images may require additional ports to be opened, such as those providing monitoring or metrics endpoints.
Additional runtime configuration is specified as YAML snippets in the charm config.
container_secrets items are provided,
and they are combined together.
container_config gets logged,
container_secrets does not. This allows you to configure customized
See config option descriptions in config.yaml.
Notes for deploying a test setup locally using microk8s:
sudo snap install juju --classic sudo snap install juju-wait --classic sudo snap install microk8s --classic sudo snap alias microk8s.kubectl kubectl microk8s.reset # Warning! Clean slate! microk8s.enable dns dashboard registry storage microk8s.status --wait-ready microk8s.config | juju add-k8s myk8s juju bootstrap myk8s juju add-model wordpress-test juju create-storage-pool operator-storage kubernetes storage-class=microk8s-hostpath juju deploy cs:~wordpress-charmers/wordpress-k8s --channel=edge wordpress juju config wordpress db_host=10.1.1.1 db_user=wp db_password=secret juju wait juju status # Shows IP address, and port is 80
- (string) Blog hostname
- (string) YAML formatted map of container config keys & values. These are generally accessed from inside the image as environment variables. Use to configure customized Wordpress images. This configuration gets logged; use container_secrets for secrets.
- (string) YAML formatted map of secrets. Works just like container_config, except that values should not be logged.
- (string) MySQL database host
- (string) MySQL database name
- (string) MySQL database user's password
- (string) MySQL database user
- (string) The docker image to install. Required. Defaults to Dockerhub wordpress:php7.3
- (string) Password to use for the configured image registry, if required
- (string) Username to use for the configured image registry, if required
- (string) Optional, YAML formatted, Wordpress configuration. It is used only during initial deployment. Changing it at later stage has no effect. If set to non empty string required keys are: user_name: admin_username admin_email: email@example.com Optionally you can also provide weblog_title: Blog title # empty by default admin_password: <secret> # autogenerated if not set blog_public: False # by default blogs are public If admin_password is not provided it will be automatically generated and stored on the operator pod in the /root directory
- (string) Ports to expose, space separated list in name:8000 format. Names are alphanumeric + hyphen. e.g. "http:80 metrics:7127"
- (string) The Kubernetes TLS secret resource name.
- (string) Akismet key. If empty, akismet will not be automatically enabled
- (string) Launchpad teams and corresponding access levels, for use with the openid plugins. Valid Wordpress access levels are: administrator, editor, author, contributor, subscriber If empty, OpenID will not be enabled. Format is key=value pairs (where key is the Launchpad team, and value is the Wordpress role) - commas separate multiple pairs. Example format: "site-sysadmins=administrator,site-editors=editor,site-executives=editor"
- (string) YAML dictionary with keys named after wordpress settings and the desired values. Please note that the settings will be reset to values provided every time hooks run