diff --git a/Makefile b/Makefile
index d3056af2..d64b390c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,6 @@
 PROJECT_NAME := m3db-operator
 OUTPUT_DIR   := out
 DOCS_OUT_DIR := site
-DEP_VERSION  := v0.6.0
 .DEFAULT_GOAL := all
 
 SELF_DIR := $(dir $(lastword $(MAKEFILE_LIST)))
diff --git a/README.md b/README.md
index 86bf5a0d..233c209e 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.6.0/bundle.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.7.0/bundle.yaml
 ```
 
 ## Managing Clusters
@@ -60,7 +60,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/bun
 Create a simple etcd cluster to store M3DB's topology:
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.6.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.7.0/example/etcd/etcd-basic.yaml
 ```
 
 Apply manifest with your zones specified for isolation groups:
diff --git a/bundle.yaml b/bundle.yaml
index 5f9a0c72..ab2663e3 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.6.0
+          image: quay.io/m3db/m3db-operator:v0.7.0
           command:
           - m3db-operator
           imagePullPolicy: Always
diff --git a/docs/getting_started/create_cluster.md b/docs/getting_started/create_cluster.md
index b36196dc..babafa36 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.6.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.7.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.6.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.7.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.6.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.7.0/example/etcd/etcd-pd.yaml
 ```
 
 ### M3DB
diff --git a/helm/m3db-operator/Chart.yaml b/helm/m3db-operator/Chart.yaml
index 942bbcd1..9010864e 100644
--- a/helm/m3db-operator/Chart.yaml
+++ b/helm/m3db-operator/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v1
 name: m3db-operator
-version: 0.6.0
+version: 0.7.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 ff17b9d8..cd9071b8 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.6.0
+  tag: v0.7.0
 environment: production