Add support for configuring hostAliases of Weaviate pod #206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hostAliases
allows you to perform hostname resolution when DNS is not available (see https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/). In my case, this is required to reach an Azure OpenAI deployment via a private endpoint (DNS not available, and correct hostname still has to be used so that certificate validation can succeed).Previously, it was not possible to configure this setting when using the Weaviate helm chart, this PR allows the user to add a configuration of the
hostAliases
used for the Weaviate pod.Note that this PR does not add this setting to other pods than the Weaviate pod. For my current use case, that is sufficient, but maybe it still would be desirable to have it applied also to other pods (maybe same behaviour as
nodeSelector
/tolerations
/affinity
with a global + module level config).