From e8eb552473ce0aaa54ec3f78353b30e6e915bf36 Mon Sep 17 00:00:00 2001
From: tenczar <nicholas.tenczar@gmail.com>
Date: Tue, 10 Jul 2018 18:10:35 -0700
Subject: [PATCH] v0.1.21 RELEASE (#567)

Update CHANGELOG.md and create release notes for v0.1.21.
---
 CHANGELOG.md                              | 19 +++++++-
 docs/_posts/2018-07-10-v0-1-21-release.md | 58 +++++++++++++++++++++++
 2 files changed, 75 insertions(+), 2 deletions(-)
 create mode 100644 docs/_posts/2018-07-10-v0-1-21-release.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
index e4b0b9d76..20e8f5965 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,9 +2,16 @@
 All notable changes to this project will be documented in this file. For more information & examples, check
 [What's New](https://vmware.github.io/dispatch/news) section on Dispatch website.
 
-## [Unreleased] - [[Git compare](https://github.com/vmware/dispatch/compare/v0.1.20...HEAD)]
+## [Unreleased] - [[Git compare](https://github.com/vmware/dispatch/compare/v0.1.21...HEAD)]
 
 ### Added
+
+### Fixed
+
+## [0.1.21] - 2018-07-10 [[Git compare](https://github.com/vmware/dispatch/compare/v0.1.20...v0.1.21)]
+
+### Added
+
 - [[Issue #518](https://github.com/vmware/dispatch/issues/518)] **Single-binary, local version of Dispatch Server:**
 This release includes a single-binary dispatch-server. You can run this server locally on your desktop without a need
 to provision Kubernetes - the only requirement is Docker. This should cover use cases like local development, proofs of concept,
@@ -14,10 +21,18 @@ and run `dispatch-server local`.
     *Note:* The local version supports all commands/resources except:
     - event drivers
     - services 
-
+- **Add Org to bulk create CLI** Orgs can now be defined in yaml files and populated in Dispatch using `dispatch create -f seed.yaml`
+- **Ingress class option** Use this option to target a different ingress controller
 
 ### Fixed
 
+- **Fixed entity store bug** Fixed a bug where the libkv-based entity store would return entities of different types if they shared the same prefix
+- **Fixed chart issue** Fixed an issue where the resources specified for an individual sub-chart didn't take precedence over the global resources
+
+### Removed
+
+- **Removed internal vCenter event driver** The vCenter event driver is no longer built in to Dispatch. You can access the vCenter event driver here https://github.com/dispatchframework/dispatch-events-vcenter
+
 ## [0.1.20] - 2018-07-03 - [[Git compare](https://github.com/vmware/dispatch/compare/v0.1.19...v0.1.20)]
 
 ### Added
diff --git a/docs/_posts/2018-07-10-v0-1-21-release.md b/docs/_posts/2018-07-10-v0-1-21-release.md
new file mode 100644
index 000000000..9550fdefd
--- /dev/null
+++ b/docs/_posts/2018-07-10-v0-1-21-release.md
@@ -0,0 +1,58 @@
+---
+layout: post
+title: "v0.1.21 Dispatch Release"
+year: 2018
+---
+
+# v0.1.21 Dispatch Release
+
+[Download v0.1.21](https://github.com/vmware/dispatch/releases/tag/v0.1.21)
+
+- [[Issue #518](https://github.com/vmware/dispatch/issues/518)] **Single-binary, local version of Dispatch Server:**
+This release includes a single-binary dispatch-server. You can run this server locally on your desktop without a need
+to provision Kubernetes - the only requirement is Docker. This should cover use cases like local development, proofs of concept,
+or a small deployment for personal needs. To use it, simply download the `dispatch-server` binary for your platform,
+and run `dispatch-server local`.
+    
+    *Note:* The local version supports all commands/resources except:
+    - event drivers
+    - services 
+
+## Add Org to bulk create CLI
+
+You can now create multiple Organizations in bulk using the create command. You can specify your orgs in a yaml file like this:
+```
+kind: Organization
+name: VMware
+---
+kind: Organization
+name: Pivotal
+---
+kind: Organization
+name: Acme Inc.
+```
+
+Then you can create these orgs using the following command, assuming your named your file `orgs.yaml`
+
+```
+$ dispatch create -f orgs.yaml
+```
+
+## Ingress class option
+
+You can now target different ingress controllers in your deployments. In your values.yaml file you can specify the class like this:
+
+```
+apiGateway:
+  host: 192.168.64.26
+dispatch:
+  host: 192.168.64.26
+  debug: true
+  image:
+    tag: v0.1.21
+    host: vmware
+  ingress:
+    class: nginx
+```
+
+This is useful for clusters with multiple ingress controllers. This class is the same kubernetes.io/ingress.class and can take any value that annotation can.
\ No newline at end of file