Update changelog for 1.4.0 release

CHANGELOG.md

@@ -4,6 +4,24 @@ All notable changes to this project will be documented in this file.
 The file is generated by [Changie](https://github.com/miniscruff/changie).
 
 
+## 1.4.0 - 2022-05-03
+### Added
+* [#189](https://github.com/vertica/vertica-kubernetes/issues/189) Additional subcluster options to better customize network load balancers
+* [#170](https://github.com/vertica/vertica-kubernetes/issues/170) Helm parameters to allow deployment of the operator from private registries
+* [#183](https://github.com/vertica/vertica-kubernetes/issues/183) Scale down will drain active connections before removing pod
+* [#171](https://github.com/vertica/vertica-kubernetes/issues/171) Allow existing serviceaccount to be used
+* [#168](https://github.com/vertica/vertica-kubernetes/issues/168) Added ability to configure RequeueAfter for upgrade reconciles. This delay can be specified through '.spec.upgradeRequeueTime' parameter. Prior to this, an online upgrade could wait upto 20 minutes before retrying.
+### Changed
+* [#187](https://github.com/vertica/vertica-kubernetes/issues/187) Change server container base image to ubuntu
+* [#188](https://github.com/vertica/vertica-kubernetes/issues/188) Set the minimum TLS version of the webhook to TLS 1.3
+* [#166](https://github.com/vertica/vertica-kubernetes/issues/166) Batch 'admintools -t db_add_node' for faster scale up
+* [#165](https://github.com/vertica/vertica-kubernetes/issues/165) Move to operator-sdk v1.18.0
+### Fixed
+* [#191](https://github.com/vertica/vertica-kubernetes/issues/191) Allow database names with uppercase characters
+* [#186](https://github.com/vertica/vertica-kubernetes/issues/186) Handle the scenario when restart is needed because the StatefulSets were deleted.  We ensure the necessary k8s objects are created before driving restart.
+* [#178](https://github.com/vertica/vertica-kubernetes/issues/178) Avoid a second cluster restart after offline upgrade has completed successfully.
+* [#176](https://github.com/vertica/vertica-kubernetes/issues/176) Upgrade path detection should allow skipping service packs
+
 ## 1.3.1 - 2022-03-02
 ### Fixed
 * [#164](https://github.com/vertica/vertica-kubernetes/issues/164) Order the environment variables that were converted from annotations.  Prior to this fix, it was quite easy to get the statefulset controller to go into a repeated rolling upgrade.  The order ensures the statefulset doesn't appear to change between reconcile cycles.

changes/1.4.0.md

@@ -0,0 +1,17 @@
+## 1.4.0 - 2022-05-03
+### Added
+* [#189](https://github.com/vertica/vertica-kubernetes/issues/189) Additional subcluster options to better customize network load balancers
+* [#170](https://github.com/vertica/vertica-kubernetes/issues/170) Helm parameters to allow deployment of the operator from private registries
+* [#183](https://github.com/vertica/vertica-kubernetes/issues/183) Scale down will drain active connections before removing pod
+* [#171](https://github.com/vertica/vertica-kubernetes/issues/171) Allow existing serviceaccount to be used
+* [#168](https://github.com/vertica/vertica-kubernetes/issues/168) Added ability to configure RequeueAfter for upgrade reconciles. This delay can be specified through '.spec.upgradeRequeueTime' parameter. Prior to this, an online upgrade could wait upto 20 minutes before retrying.
+### Changed
+* [#187](https://github.com/vertica/vertica-kubernetes/issues/187) Change server container base image to ubuntu
+* [#188](https://github.com/vertica/vertica-kubernetes/issues/188) Set the minimum TLS version of the webhook to TLS 1.3
+* [#166](https://github.com/vertica/vertica-kubernetes/issues/166) Batch 'admintools -t db_add_node' for faster scale up
+* [#165](https://github.com/vertica/vertica-kubernetes/issues/165) Move to operator-sdk v1.18.0
+### Fixed
+* [#191](https://github.com/vertica/vertica-kubernetes/issues/191) Allow database names with uppercase characters
+* [#186](https://github.com/vertica/vertica-kubernetes/issues/186) Handle the scenario when restart is needed because the StatefulSets were deleted.  We ensure the necessary k8s objects are created before driving restart.
+* [#178](https://github.com/vertica/vertica-kubernetes/issues/178) Avoid a second cluster restart after offline upgrade has completed successfully.
+* [#176](https://github.com/vertica/vertica-kubernetes/issues/176) Upgrade path detection should allow skipping service packs