Release notes for v0.19.0

Changelog since v0.18.2

Changes by Kind

Feature

remove cert-manager and attach AWS ACM in the public Nginx deployment to use SSL certificates (#214, @cpanato)
Moves the DNS Registration as a first step in the process. The reason is to give the Cert Manager a head start to register the installation certificate.
Adds a InstallationStateCreationFinalTasks state, which handles checks needed before setting the installation to stable. Currently, there is a single check to make sure that the SSL certificate is approved.
Adapts tests to the state changes (#194, @stylianosrigas)

Other (Bug, Cleanup or Flake)

Create encryption keys with tags.
Find encryption keys using resource groups tagging api.
Reuse already existent keys when creating RDS instance.
Validating that only one key in Enabled state exists when creating instance.
Remove keys when installation is deleted.
Eliminate the need for creating key alias which was the source for leaking KMS resources. (#202, @gsagula)
Add missing default values for post cluster installation (#211, @cpanato)
Aws: set log to DEBUG from AWS Session (#203, @gigawhitlocks)
Check group deletion state before joining installation (#195, @gabrieljackson)

Uncategorized

Added a new database implementation for handling multiple tenants in a single RDS DB cluster.
Added new table MultitenantDatabase so provisioner can keep track of database installations in each RDS cluster.
Provisioner will always do lookups in the MultitenantDatabase table first and, if nothing is available, it will try to fetch the resources directly from RDS via resource tags.
RDS tags are defined in tools/aws/constants.go, however the provisioner does not create them in AWS since this work is done via Terraform.
Provisioner uses these tags to identify the correct RDS clusters in order to install new databases.
Tag:Counter is maintained by the provisioner. The value is incremented and decremented on every new installation or uninstallation respectively.
There is a hardcoded limit in the number database installations that each RDS cluster can take. This limit is referenced by a constant also defined in tools/aws/constants.go.
The multitenant database follows the same design pattern of all other databases. In fact, it implements the same interface.
Small modifications were done to the signature of some the interface's methods . (#209, @gsagula)
Changed the multi-tenant database logic to acquire locks using the instance ID instead of the installation ID.
Removed the logic used by the multi-tenant database to auto-release rows in a permanent locked state. This should be done manually by the operator. (#215, @gsagula)
Add cluster resize functionality (#213, @gabrieljackson)
Added --dev flag for a development mode with sane defaults for running the provisioner server during development (#205, @gigawhitlocks)
Fixed a bug causing --dev to not output DEBUG logs (#210, @gigawhitlocks)
Optimized UtilityGroup installation at cluster creation time (#204, @gigawhitlocks)