Ghost is one of the most versatile open source content management systems on the market.
$ helm install stable/ghostThis chart bootstraps a Ghost 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 for the database requirements of the Ghost application.
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
To install the chart with the release name my-release:
$ helm install --name my-release stable/ghostThe command deploys Ghost on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip: List all releases using
helm list
To uninstall/delete the my-release deployment:
$ helm delete my-releaseThe command removes all the Kubernetes components associated with the chart and deletes the release.
The following tables lists the configurable parameters of the Ghost chart and their default values.
| Parameter | Description | Default |
|---|---|---|
image |
Ghost image | bitnami/ghost:{VERSION} |
imagePullPolicy |
Image pull policy | Always if image tag is latest, else IfNotPresent |
ghostHost |
Ghost host to create application URLs | nil |
ghostPort |
Ghost port to create application URLs along with host | 80 |
ghostLoadBalancerIP |
loadBalancerIP for the Ghost Service |
nil |
ghostUsername |
User of the application | user |
ghostPassword |
Application password | Randomly generated |
ghostEmail |
Admin email | [email protected] |
ghostBlogTitle |
Ghost Blog name | User's Blog |
mariadb.mariadbRootPassword |
MariaDB admin password | nil |
serviceType |
Kubernetes Service type | LoadBalancer |
persistence.enabled |
Enable persistence using PVC | true |
persistence.storageClass |
PVC Storage Class for Ghost volume | nil (uses alpha storage annotation) |
persistence.accessMode |
PVC Access Mode for Ghost volume | ReadWriteOnce |
persistence.size |
PVC Storage Request for Ghost volume | 8Gi |
resources |
CPU/Memory resource requests/limits | Memory: 512Mi, CPU: 300m |
The above parameters map to the env variables defined in bitnami/ghost. For more information please refer to the bitnami/ghost image documentation.
Note:
For the Ghost application function correctly, you should specify the
ghostHostparameter to specify the FQDN (recommended) or the public IP address of the Ghost service.Optionally, you can specify the
ghostLoadBalancerIPparameter to assign a reserved IP address to the Ghost service of the chart. However please note that this feature is only available on a few cloud providers (f.e. GKE).To reserve a public IP address on GKE:
$ gcloud compute addresses create ghost-public-ipThe reserved IP address can be associated to the Ghost service by specifying it as the value of the
ghostLoadBalancerIPparameter while installing the chart.
Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,
$ helm install --name my-release \
--set ghostUsername=admin,ghostPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/ghostThe above command sets the Ghost administrator account username and password to admin and password respectively. Additionally it sets the MariaDB root user password to secretpassword.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml stable/ghostTip: You can use the default values.yaml
The Bitnami Ghost image stores the Ghost data and configurations at the /bitnami/ghost and /bitnami/apache paths of the container.
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.