diff --git a/CHANGELOG.md b/CHANGELOG.md
index ee91412c..8b018b50 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.11.0
+
+0.11.0 ensures the operator is compatible with clusters running M3 1.0. It removes usage of M3 APIs that were deprecated
+as part of that release.
+
+* [FEATURE] Allow AggregationOptions to be set for a namespace. ([#248][248])
+* [ENHANCEMENT] Update use of now deleted namespace urls in operator ([#247][247])
+* [ENHANCEMENT] Add calls to /namespace/ready if supported by coordinator ([#245][245])
+
+
 ## 0.10.0
 
 0.10.0 adds initial support for safe, graceful cluster upgrades. See [the upgrade
@@ -287,3 +297,6 @@ If using a custom configmap, this same change will require a modification to you
 [230]: https://github.com/m3db/m3db-operator/pull/230
 [233]: https://github.com/m3db/m3db-operator/pull/233
 [242]: https://github.com/m3db/m3db-operator/pull/242
+[245]: https://github.com/m3db/m3db-operator/pull/245
+[247]: https://github.com/m3db/m3db-operator/pull/247
+[248]: https://github.com/m3db/m3db-operator/pull/248
diff --git a/README.md b/README.md
index 417b8e91..8ffd6d7c 100644
--- a/README.md
+++ b/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.10.0/bundle.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.11.0/bundle.yaml
 ```
 
 ## Managing Clusters
@@ -58,7 +58,7 @@ kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.10.0/bu
 Create a simple etcd cluster to store M3DB's topology:
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.10.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.11.0/example/etcd/etcd-basic.yaml
 ```
 
 Apply manifest with your zones specified for isolation groups:
diff --git a/bundle.yaml b/bundle.yaml
index 26ec81ca..4d445ad0 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.10.0
+          image: quay.io/m3db/m3db-operator:v0.11.0
           command:
           - m3db-operator
           imagePullPolicy: Always
diff --git a/docs/getting_started/create_cluster.md b/docs/getting_started/create_cluster.md
index 652327fd..e0695fb7 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.10.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.11.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.10.0/example/etcd/etcd-basic.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.11.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.10.0/example/etcd/etcd-pd.yaml
+kubectl apply -f https://raw.githubusercontent.com/m3db/m3db-operator/v0.11.0/example/etcd/etcd-pd.yaml
 ```
 
 ### M3DB
diff --git a/helm/m3db-operator/Chart.yaml b/helm/m3db-operator/Chart.yaml
index f75e5d9e..9b0ac2db 100644
--- a/helm/m3db-operator/Chart.yaml
+++ b/helm/m3db-operator/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v1
 name: m3db-operator
-version: 0.10.0
+version: 0.11.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 9c63bb4f..e8ec76bb 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.10.0
+  tag: v0.11.0
 environment: production