From 284278703da69b240314440f64b417bf01cf6136 Mon Sep 17 00:00:00 2001
From: Robert Blaine <4052340+rblaine95@users.noreply.github.com>
Date: Mon, 5 Apr 2021 17:01:17 +0000
Subject: [PATCH] Major version bump, fix #55 (#56)

---
 README.md                   | 19 +++++++++++++++++++
 charts/verdaccio/Chart.yaml |  2 +-
 2 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 72ddc9b..680ffc9 100644
--- a/README.md
+++ b/README.md
@@ -172,3 +172,22 @@ $ helm install npm \
     --set persistence.existingClaim=PVC_NAME \
     verdaccio/verdaccio
 ```
+
+### Migrating chart 2.x -> 3.x
+Due to some breaking changes in Selector Labels and Security Contexts in Chart `3.0.0` you will need to migrate when upgrading.
+
+First off, the `securityContext.enabled` field has been removed.  
+In addition to this, `fsGroup` is not a valid Container Security Context field and has been migrated to the `podSecurityContext` instead.
+```diff
+# values.yaml
+podSecurityContext:
++  fsGroup: 101
+ securityContext:
+-  enabled: true
+-  fsGroup: 101
+   runAsUser: 10001
+```
+
+Secondly, the `apps.v1.Deployment.spec.selector` field is immutable and changes were made to Selector Labels which tries to update this.  
+To get around this, you will need to `kubectl delete deployment $deploymentName` before doing a `helm upgrade`  
+So long as your PVC is not destroyed, the new deployment will be rolled out with the same PVC as before and your data will remain intact.
diff --git a/charts/verdaccio/Chart.yaml b/charts/verdaccio/Chart.yaml
index 0734a12..194a602 100644
--- a/charts/verdaccio/Chart.yaml
+++ b/charts/verdaccio/Chart.yaml
@@ -1,7 +1,7 @@
 apiVersion: v2
 description: A lightweight private npm proxy registry (sinopia fork)
 name: verdaccio
-version: 2.1.0
+version: 3.0.0
 appVersion: 4.12.0
 home: https://verdaccio.org
 icon: https://cdn.verdaccio.dev/logos/default.png