weaviate/weaviate 0.21.2 on GitHub

Docker image/tag: semitechnologies/weaviate:0.21.2
See also: example docker compose files in english and dutch.

Breaking Changes

none

Live and Readyness Checks added (#674)
Previously users have used existing endpoints, such as /v1/meta for health checks, however this lead to issues when using auth schemes, such as OIDC, as the meta endpoint would be behind auth.
This release introduces dedicated live and readyness endpoints regardless of auth status:
/v1/.well-known/live responds with 204 No Content when the weaviate instance is alive
/v1/.well-known/ready responds with 204 No Content when the weaviate instance is ready
Note: As of now there are no separate live/ready requirements. The app is considered both live and ready as soon as Weaviate is able to serve the REST API. This might change in the future for the readyness endpoint, i.e. we might perform additional checks to determine if the particular instance should receive traffic. It is therefore recommended to explicitly use the liveness endpoint for liveness checks and the readiness endpoint for readiness checks - even if they behave the same at the moment.

none