Skip to content

Commit

Permalink
[release] Prepare 0.6.0 release (#207)
Browse files Browse the repository at this point in the history
  • Loading branch information
schallert authored Mar 19, 2020
1 parent 182be89 commit 73a10cd
Show file tree
Hide file tree
Showing 7 changed files with 20 additions and 9 deletions.
11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Changelog

## 0.6.0

0.6.0 includes a fix to allow M3DB nodes to receive traffic while bootstrapping, and an option to limit what namespaces
the operator watches resources in, which should greatly help users running the operator in massive Kubernetes clusters.

* [ENHANCEMENT] Ensure dbnodes in DNS when bootstrapping ([#206][206])
* [FEATURE] Add one option able to only watch one specific namespace ([#205][205])


## 0.5.0

0.5.0 includes a bug fix for passing cluster annotations to pods, as well as a backwards-compatible addition of a new
Expand Down Expand Up @@ -178,3 +187,5 @@ If using a custom configmap, this same change will require a modification to you
[194]: https://github.com/m3db/m3db-operator/pull/194
[196]: https://github.com/m3db/m3db-operator/pull/196
[197]: https://github.com/m3db/m3db-operator/pull/197
[205]: https://github.com/m3db/m3db-operator/pull/205
[206]: https://github.com/m3db/m3db-operator/pull/206
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
PROJECT_NAME := m3db-operator
OUTPUT_DIR := out
DOCS_OUT_DIR := site
DEP_VERSION := v0.5.0
DEP_VERSION := v0.6.0
.DEFAULT_GOAL := all

SELF_DIR := $(dir $(lastword $(MAKEFILE_LIST)))
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.5.0/bundle.yaml
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/bundle.yaml
```

## Managing Clusters
Expand All @@ -60,7 +60,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.5.0/bun
Create a simple etcd cluster to store M3DB's topology:

```
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.5.0/example/etcd/etcd-basic.yaml
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/example/etcd/etcd-basic.yaml
```

Apply manifest with your zones specified for isolation groups:
Expand Down
2 changes: 1 addition & 1 deletion bundle.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ spec:
runAsGroup: 65534
containers:
- name: m3db-operator
image: quay.io/m3db/m3db-operator:v0.5.0
image: quay.io/m3db/m3db-operator:v0.6.0
command:
- m3db-operator
imagePullPolicy: Always
Expand Down
6 changes: 3 additions & 3 deletions docs/getting_started/create_cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.5.0/example/etcd/etcd-pd.yaml
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/example/etcd/etcd-pd.yaml
```

We recommend modifying the `storageClassName` in the manifest to one that matches your cloud provider's fastest remote
Expand Down Expand Up @@ -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.5.0/example/etcd/etcd-basic.yaml
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/example/etcd/etcd-basic.yaml

# Verify etcd health once pods available
kubectl exec etcd-0 -- env ETCDCTL_API=3 etcdctl endpoint health
Expand All @@ -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.5.0/example/etcd/etcd-pd.yaml
kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/example/etcd/etcd-pd.yaml
```

### M3DB
Expand Down
2 changes: 1 addition & 1 deletion helm/m3db-operator/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v1
name: m3db-operator
version: 0.5.0
version: 0.6.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
#
Expand Down
2 changes: 1 addition & 1 deletion helm/m3db-operator/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,5 @@ operator:
name: m3db-operator
image:
repository: quay.io/m3db/m3db-operator
tag: v0.5.0
tag: v0.6.0
environment: production

0 comments on commit 73a10cd

Please sign in to comment.