Skip to content

Conversation

@geekgonecrazy
Copy link

As part of being able to auto discover weaviate in cluster being able to append labels to the service helps a lot

@weaviate-git-bot
Copy link

To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge.

beep boop - the Weaviate bot 👋🤖

PS:
Are you already a member of the Weaviate Slack channel?

@antas-marcin
Copy link
Collaborator

If you want us to merge your PR you need to agree to our CLA. Simply making a I agree with CLA comment does the trick :)

Comment on lines +9 to +11
{{- with .Values.service.labels }}
{{ toYaml . | indent 4 }}
{{- end }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add tests for this? You can use check_string_existence method for that

Comment on lines +8 to +10
{{- with .Values.service.labels }}
{{ toYaml . | indent 4 }}
{{- end }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also add a separate test for this case?

@geekgonecrazy
Copy link
Author

I agree with CLA

@geekgonecrazy
Copy link
Author

geekgonecrazy commented Jul 16, 2024

We actually ended up going with another vector database. So my attention has moved on from here and I won't be pushing this forward.

But i've got "Allow edits by maintainers" checked and will happily give anyone else that wants to finish this contributor access.

Also feel free to just close. No feelings hurt here. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants