From 606ecd3ffe47608f81989c7d8dcfee3b603d9cdb Mon Sep 17 00:00:00 2001 From: Matt Schallert Date: Thu, 13 Feb 2020 14:43:50 -0500 Subject: [PATCH] [release] 0.4.0 changelog + manifest changes (#195) --- CHANGELOG.md | 13 +++++++++++++ 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, 21 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4389dd9f..53f661cd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,14 @@ # Changelog +## 0.4.0 + +0.4.0 includes minor feature additions that won't have any change in behavior for existing users. + +* [FEATURE] Support custom env vars in cluster spec ([#194][194]) +* [ENHANCEMENT] Add topic client ([#190][190]) +* [ENHANCEMENT] Migrate to Go modules ([#188][188]) +* [FEATURE] Allow overriding node endpoint format ([#183][183]) + ## 0.3.0 0.3.0 is focused on some behind the scenes reliability improvements. Changes such as using purpose-build M3DB health @@ -154,3 +163,7 @@ If using a custom configmap, this same change will require a modification to you [167]: https://github.com/m3db/m3db-operator/pull/167 [169]: https://github.com/m3db/m3db-operator/pull/169 [181]: https://github.com/m3db/m3db-operator/pull/181 +[183]: https://github.com/m3db/m3db-operator/pull/183 +[188]: https://github.com/m3db/m3db-operator/pull/188 +[190]: https://github.com/m3db/m3db-operator/pull/190 +[194]: https://github.com/m3db/m3db-operator/pull/194 diff --git a/README.md b/README.md index 6b46c81e..5d9692a5 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.3.0/bundle.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.4.0/bundle.yaml ``` ## Managing Clusters @@ -60,7 +60,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.3.0/bun Create a simple etcd cluster to store M3DB's topology: ``` -kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.3.0/example/etcd/etcd-basic.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.4.0/example/etcd/etcd-basic.yaml ``` Apply manifest with your zones specified for isolation groups: diff --git a/bundle.yaml b/bundle.yaml index 30164556..a8389eac 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.3.0 + image: quay.io/m3db/m3db-operator:v0.4.0 command: - m3db-operator imagePullPolicy: Always diff --git a/docs/getting_started/create_cluster.md b/docs/getting_started/create_cluster.md index 8f39a5f6..8c6b55b7 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.3.0/example/etcd/etcd-pd.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.4.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.3.0/example/etcd/etcd-basic.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.4.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.3.0/example/etcd/etcd-pd.yaml +kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.4.0/example/etcd/etcd-pd.yaml ``` ### M3DB diff --git a/helm/m3db-operator/Chart.yaml b/helm/m3db-operator/Chart.yaml index a4c4d5e9..902857d3 100644 --- a/helm/m3db-operator/Chart.yaml +++ b/helm/m3db-operator/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v1 name: m3db-operator -version: 0.3.0 +version: 0.4.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 80e1a2df..0f7c9db8 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.3.0 + tag: v0.4.0 environment: production