Releases: streamnative/terraform-aws-cloud
v0.3.0
v0.2.0
v0.2.0 Release Notes
Changes
Previously, OLM was the default method for installing operators on the cluster, however the StreamNative operator catalog is not ready for general use.
In this release, we now default to installing the necessary operators via Helm. If using OLM is desired for testing purposes, setting disable_olm = false
in the module instantiation will turn off installing the operators via Helm, and use OLM instead.
Improvements
Prior to v0.2.0 there was no way to control the helm_release
used for the Operators. Additional inputs were added for each operator, as well as the expected defaults.
Improvements were also made to the operator_settings
variables that exist for each operator being managed by Helm, which are key value pairs passed to the set
argument for the helm_release
.
If any additional customization are required for the helm chart, one needs only to pass them through during the module instantiation. For instance, the Prometheus operator installation can be customized by overriding the default values (contained in the services.tf
file) being passed to the helm release:
prometheus_operator_settings = {
"prometheus.enabled" = "true"
}
Which will be passed to the helm_release
as:
set {
name = "prometheus.enabled"
value = "true"
}
Breaking Changes
The following potentially breaking changes were made:
- Changed
var.enable_olm
tovar.disable_olm
. Defaults to true, which turns off OLM.q - Changed
var.enable_vault_operator
tovar.enable_vault
, as thehelm_release
for Vault is currently the only supported means of installing the operator. - Removed
var.cert_manager_service_account_annotations
. Usevar.cert_manager_settings
instead to pass values to the helm release - Removed
var.enable_olm_subscriptions
. Subscriptions to the required operators are now created by default if using OLM
initial module release
v0.1.0 Initial commit