From f4c72197c95d728af2b02582652a862f58e65ac1 Mon Sep 17 00:00:00 2001 From: Matt Schallert Date: Thu, 23 Jul 2020 14:25:16 -0400 Subject: [PATCH] [changelog] Prep v0.9.0 release (#228) --- CHANGELOG.md | 10 ++++++++++ README.md | 4 ++-- bundle.yaml | 2 +- docs/getting_started/create_cluster.md | 6 +++--- helm/m3db-operator/Chart.yaml | 2 +- helm/m3db-operator/values.yaml | 2 +- 6 files changed, 18 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ea0b3b1f..db7ad683 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,13 @@ # Changelog +## 0.9.0 + +0.9.0 includes support for attaching a custom Kubernetes service account to M3DB pods (enabling use of +PodSecurityPolicies and the like), and an improvement in how new StatefulSets are created when others are unhealthy. + +* [FEATURE] Support custom svc account for M3DB pods ([#225][225]) +* [ENHANCEMENT] Create missing statefulsets before waiting for ready ([#227][227]) + ## 0.8.0 0.8.0 includes changes to improve operator performance and reduce load on Kubernetes API servers. The operator will only @@ -223,3 +231,5 @@ If using a custom configmap, this same change will require a modification to you [220]: https://github.com/m3db/m3db-operator/pull/220 [221]: https://github.com/m3db/m3db-operator/pull/221 [222]: https://github.com/m3db/m3db-operator/pull/222 +[225]: https://github.com/m3db/m3db-operator/pull/225 +[227]: https://github.com/m3db/m3db-operator/pull/227 diff --git a/README.md b/README.md index 6f2eff37..1ae13cfd 100644 --- a/README.md +++ b/README.md @@ -50,7 +50,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.8.0/bundle.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.9.0/bundle.yaml ``` ## Managing Clusters @@ -60,7 +60,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.8.0/bun Create a simple etcd cluster to store M3DB's topology: ``` -kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.8.0/example/etcd/etcd-basic.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.9.0/example/etcd/etcd-basic.yaml ``` Apply manifest with your zones specified for isolation groups: diff --git a/bundle.yaml b/bundle.yaml index db2456c0..d68e09bf 100644 --- a/bundle.yaml +++ b/bundle.yaml @@ -80,7 +80,7 @@ spec: runAsGroup: 65534 containers: - name: m3db-operator - image: quay.io/m3db/m3db-operator:v0.8.0 + image: quay.io/m3db/m3db-operator:v0.9.0 command: - m3db-operator imagePullPolicy: Always diff --git a/docs/getting_started/create_cluster.md b/docs/getting_started/create_cluster.md index 2a2a2e3b..732e50be 100644 --- a/docs/getting_started/create_cluster.md +++ b/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.8.0/example/etcd/etcd-pd.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.9.0/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.8.0/example/etcd/etcd-basic.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.9.0/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.8.0/example/etcd/etcd-pd.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.9.0/example/etcd/etcd-pd.yaml ``` ### M3DB diff --git a/helm/m3db-operator/Chart.yaml b/helm/m3db-operator/Chart.yaml index c32f6767..745f138a 100644 --- a/helm/m3db-operator/Chart.yaml +++ b/helm/m3db-operator/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v1 name: m3db-operator -version: 0.8.0 +version: 0.9.0 # 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 # diff --git a/helm/m3db-operator/values.yaml b/helm/m3db-operator/values.yaml index 74012cb0..46a89a16 100644 --- a/helm/m3db-operator/values.yaml +++ b/helm/m3db-operator/values.yaml @@ -2,5 +2,5 @@ operator: name: m3db-operator image: repository: quay.io/m3db/m3db-operator - tag: v0.8.0 + tag: v0.9.0 environment: production