Skip to content

Latest commit

 

History

History
109 lines (68 loc) · 5.53 KB

CHANGELOG.md

File metadata and controls

109 lines (68 loc) · 5.53 KB
Raw

Changelog

[v0.8.0]

Added

  • Added test pods supporting helm test command
    • There are multiple test pods, some of which run based on what is possible to test in the selected chart configuration
  • Added support for tenant management API (ingress)

Changed

  • Bumped version of sf-tenant-management subchart
    • since the chart was renamed all references to previous name were changes

Breaking change

  • Changed default behavior for creating Authentication configuration. If you like to continue managing the previously created Authentication config map please use the configurations.apiAuth.existingConfigMapName field. Otherwise the ConfigMap will be managed by the helm chart using the values provided in configurations.apiAuth
    • This change also includes renaming previous field configurations.apiAuth.configName -> configurations.apiAuth.existingConfigMapName

[v0.7.1]

Changed

  • Fixed condition for DbSynchronizationLeader deployment

[v0.7.0]

Added

  • Support for DbSynchronizationLeader has been added

Changed

  • Bumped version of sf-tenant-operator to 0.3.0

[v0.6.0]

Changed

  • Bumped version of SmartFace Station to 1.22

Breaking change

  • deployment of SmartFace Station is now disabled by default. To reenable previous behavior with deploying SmartFace Station please set the station.enabled value to true.
    • previous behavior with enabled SmartFace Station caused the installation of helm chart with default values to fail on validation because SmartFace Station is currently dependant on SmartFace API with enabled authentication, which in turn requires the existence of external authentication provider and correct configuration of relevant SmartFace services

[v0.5.2]

Changed

  • Bumped version of SmartFace Platform to 4.24

[v0.5.1]

Changed

  • Bumped version of SmartFace Platform and SmartFace Station

[v0.5.0]

Added

  • Support for using minio subchart in place of S3 bucket
    • This is now default behavior of the helm chart
  • Support for using postgresql subchart in place of externally managed PgSQL instance
    • This is now default behavior of the helm chart

Breaking change

  • MinIO subchart is enabled and used by default. To keep using S3 bucket managed outside of this helm chart please set the minio.enabled value to false and provide configuration details via configurations.s3
  • Postgresql subchart is enabled and used by default. To keep using PgSQL instance managed outside of this helm chart please set the postgresql.enabled value to false and provide configuration details via configurations.database

[v0.4.0]

Added

  • Common labels with option to specify custom labels/annotation for objects
  • PodDisruptionBudgets for deployments that can be scaled
  • Support for custom KEDA triggers
  • Existing configmap for rabbitMQ and S3 is no longer necessary and the chart can create them from provided values, which is also the new default behavior for S3

Breaking change

  • Changed default behavior for creating S3 configuration. If you like to continue managing the previously created S3 config map please use the configurations.s3.existingConfigMapName field. Otherwise the ConfigMap will be managed by the helm chart using the values provided in configurations.s3
    • The ConfigMap keys for existing config map are no longer configurable, so if you want to keep using the ConfigMap not managed by this chart then please make sure that the key match what the helm chart expects
  • Some values have had their keys changed or moved around:
    • database secret -> value key changed from configurations.database.secretName to configurations.database.existingSecretName
    • rmq secret values moved to auth parent object -> from rabbitmq.existingSecretName to rabbitmq.auth.existingSecretName and rabbitmq.secretKey to rabbitmq.auth.secretKey
    • rmq configuration reworked -> value key rabbitmq.configMapName and rabbitmq.mqttConfigMapName replaced with existingConfigMapName key in rabbitmq.rmqConfiguration and rabbitmq.mqttConfiguration objects respectively
    • mqtt dns host configuration changed -> value key rabbitmq.mqttDnsHost replaced with object with key rabbitmq.mqttPublicService that can be disabled
    • deployment selectors changed
    • autoscaling configuration reworked -> moved rmq and cron configuration related to services their respective sub-objects e.g. for detector from autoscaling.detector to autoscaling.cron.detector and autoscaling.rmq.detector
  • Deployment label selectors and pod labels were modified to use a more standardized approach. Unfortunately since label selector are immutable and thus the helm release cannot be upgraded. Please first use helm uninstall and a fresh helm install for upgrading. For more information see the official documentation

[v0.3.0]

Added

  • Support for pushing watchlist data to edge streams via EdgeStreamsStateSynchronizer

[v0.2.0]

Added

  • Initial implementation
  • Chart can be configured to support following scenarios:
    • Lightweight Face Identification System (LFIS) - single-tenant and multi-tenant
    • Edge stream processing - single tenant only
  • Chart can be configured to use externally-managed rabbitmq (e.g. AmazonMQ) or deploy a rabbitmq subchart