diff --git a/stable/ghost/Chart.yaml b/stable/ghost/Chart.yaml
index d485a23d6843..1b110eec39dd 100644
--- a/stable/ghost/Chart.yaml
+++ b/stable/ghost/Chart.yaml
@@ -1,5 +1,5 @@
 name: ghost
-version: 4.0.21
+version: 5.0.0
 appVersion: 2.1.3
 description: A simple, powerful publishing platform that allows you to share your
   stories with the world
diff --git a/stable/ghost/README.md b/stable/ghost/README.md
index 369de25405c7..9ba569d69e0d 100644
--- a/stable/ghost/README.md
+++ b/stable/ghost/README.md
@@ -127,3 +127,15 @@ The [Bitnami Ghost](https://github.com/bitnami/bitnami-docker-ghost) image store
 
 Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
 See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
+
+## Upgrading
+
+### To 5.0.0
+
+Backwards compatibility is not guaranteed unless you modify the labels used on the chart's deployments.
+Use the workaround below to upgrade from versions previous to 5.0.0. The following example assumes that the release name is ghost:
+
+```console
+$ kubectl patch deployment ghost-ghost --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+$ kubectl delete statefulset ghost-mariadb --cascade=false
+```
diff --git a/stable/ghost/templates/deployment.yaml b/stable/ghost/templates/deployment.yaml
index fa1f5216e78c..1c30f8d0ed77 100644
--- a/stable/ghost/templates/deployment.yaml
+++ b/stable/ghost/templates/deployment.yaml
@@ -9,6 +9,10 @@ metadata:
     release: "{{ .Release.Name }}"
     heritage: "{{ .Release.Service }}"
 spec:
+  selector:
+    matchLabels:
+      app: {{ template "ghost.fullname" . }}
+      release: "{{ .Release.Name }}"
   replicas: 1
   template:
     metadata: