Prep changelog for v0.12.1 release (#264)

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.12.1
+
+0.12.1 fixes bugs related to cluster startup and update due to the release of M3DB 1.0.
+
+* [ENHANCEMENT] Wait for replica to update pods before processing next statefulset update ([#260][260])
+* [BUGFIX] Ensure fresh cluster startup succeeds in M3 1.0+ ([#261][261])
+
 ## 0.12.0
 
 0.12.0 adds support for running sidecar containers in the M3DB pods and ensures
@@ -318,3 +325,5 @@ If using a custom configmap, this same change will require a modification to you
 [248]: https://github.com/m3db/m3db-operator/pull/248
 [250]: https://github.com/m3db/m3db-operator/pull/250
 [253]: https://github.com/m3db/m3db-operator/pull/253
+[260]: https://github.com/m3db/m3db-operator/pull/260
+[261]: https://github.com/m3db/m3db-operator/pull/261

README.md

@@ -48,7 +48,7 @@ helm install m3db/m3db-operator --namespace m3db-operator
 With `kubectl` (will install in the `default` namespace):
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/bundle.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.1/bundle.yaml
 ```
 
 ## Managing Clusters
@@ -58,7 +58,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/bu
 Create a simple etcd cluster to store M3DB's topology:
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.1/example/etcd/etcd-basic.yaml
 ```
 
 Apply manifest with your zones specified for isolation groups:

bundle.yaml

@@ -80,7 +80,7 @@ spec:
         runAsGroup: 65534
       containers:
         - name: m3db-operator
-          image: quay.io/m3db/m3db-operator:v0.12.0
+          image: quay.io/m3db/m3db-operator:v0.12.1
           command:
           - m3db-operator
           imagePullPolicy: Always

docs/getting_started/create_cluster.md

@@ -13,7 +13,7 @@ clusters, see the docs on [node affinity][node-affinity].
 
 Create an etcd cluster with persistent volumes:
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.1/example/etcd/etcd-pd.yaml
 ```
 
 We recommend modifying the `storageClassName` in the manifest to one that matches your cloud provider's fastest remote
@@ -84,7 +84,7 @@ available, this will create a cluster that will not use persistent storage and w
 the pods die:
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.1/example/etcd/etcd-basic.yaml
 
 # Verify etcd health once pods available
 kubectl exec etcd-0 -- env ETCDCTL_API=3 etcdctl endpoint health
@@ -94,7 +94,7 @@ kubectl exec etcd-0 -- env ETCDCTL_API=3 etcdctl endpoint health
 If you have remote storage available and would like to jump straight to using it, apply the following manifest for etcd
 instead:
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.12.1/example/etcd/etcd-pd.yaml
 ```
 
 ### M3DB

helm/m3db-operator/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 name: m3db-operator
-version: 0.12.0
+version: 0.12.1
 # TODO(PS) - helm has issues with GKE's SemVer
 # Error: Chart requires kubernetesVersion: >=1.10.6 which is incompatible with Kubernetes v1.10.7-gke.2
 #

helm/m3db-operator/values.yaml

@@ -2,5 +2,5 @@ operator:
   name: m3db-operator
 image:
   repository: quay.io/m3db/m3db-operator
-  tag: v0.12.0
+  tag: v0.12.1
 environment: production