v0.3.1 - Fix possible yaml indentation issues

Fixes

• config.yaml indentation issues
  Depending on the settings, the previous release could lead to cases where the yaml indentation was such that the config map wasn't mounted as a yaml file, but as a string, leading to further issues. This fix makes use of the tips outlined in helm/helm#3854 to address this.

v0.3.0 - Better configurability through values.yaml

New Features

• Weaviate config now managable through values.yaml (#5)
  Note: Currently we only expose the config that does not include service discovery information. Anything with service hosts needs templating (as the service names depend on the .Release.Name). However, the discovery information is configured to work out of the box, so most likely users will want to change the other config fields
• Config includes authentication and authorization fields (#6)
  Building on the point above, we can now also configure all auth related info through values.yaml

Changes

• Default weaviate version updated
  The chart defaults to 0.12.71-7cdf2dd now which adds the admin_list authorization option

v0.2.3 - Fix: Incorrect config key leads to no results on /things and /actions

Fixes

• weaviate/weaviate#869 Incorrect config key leads to no results on /things and /actions
  This fixed an issue where an incorrect default config key in the /weaviate-config/conf.yaml would set the maximum query result limit to 0, thus always leading to empty responses.

v0.2.2 - Point to new image locations

Fixes

• #3 Adapt to new repo location of weaviate
  The weaviate GitHub repo and Dockerhub images were moved. This release updates the default image locations.

v0.2.1 - Fix DNS name issues

Fixes

• #2: Bug: DNS names hard-coded, not based on chart name
  The previous version had some dns names hard-coded on the assumption that the release was named weaviate by the user. If you chose another name, network communication between Janus<>Cassandra and Weaviate<>etcd would break. This addresses this, by using the release name as part of the dns names for service discovery.

v0.2.0 - Set Default Auth Scheme to Anonymous Access

Changes

• Set Default Auth Scheme to Anonymous Access
  Previously the configuration had no default auth scheme set, which would mean, unless the user explicitly overwrote the config, the setup would not be able to start up. This release sets "Anonymous Auth" as default. For more information about Weaviate's auth schemes, check the chapter about Authentication in the docs.

Fixes

• Remove obsolete config options
  The previous version contained config option that have been removed and therefore had no more effect. This version cleans this up

Known Limitations

• Content of config file in template
  The config file (/weaviate-config/conf.yaml) is being mounted from a config map. This is great, as it allows for easy changing of the config. However, the config map itself is currently not created based on user input from values.yaml, but rather hard-coded in a template file. This means you'd have to create your own chart and overwrite the template file. This should be moved into the values.yaml for easy config changes in a future release.
  Update: This limitation was fixed in v0.3.0

v0.1.4 - Fix config file name inconsistencies

Fixes

• Fix inconsistencies between config file name in configMap and deployment
  Previously the file was called weaviate-conf.yaml in one place and weaviate.conf.yaml in another. Since it is already mounted into the folder /weaviate-config, the file is now simply called conf.yaml both in the config map and the deployment resource.

v0.1.3 - Fix startup arguments

Fixes

• Fix incorrect startup arguments to weaviate
  While the previous fix (v0.1.2) addressed the structure of the config file, this release also addresses the default startup parameters.

v0.1.2 - Fix Weaviate Configuration File Structure

Fixes

• Fix config.yaml structure
  The previous version of the chart was not yet compatible with the changes introduced in weaviate/weaviate#826. This release fixes the incompatibilities

v0.1.1 - Disable Spark Setup by default

Changes

• Spark deployment is now disabled by default
  It was always meant to be optional, but was accidentally activated by default in the previous release. This drastically reduces the resource requirements for users who don't need a Spark-based analytics setup. Those who still want to use Spark, can turn it on as outlined in the values.yaml file.