We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi !
Since Annotations are not available in Endpoints metadata, I suggest using only label for this case. This is 2 kinds of possible consul tags :
mytag
secondtag
foo=bar
cluster=acme
kube2consul should support both :)
I made a very quick-and-dirty working proof of concept here : https://github.com/BarthV/kube2consul/tree/using-labels
This is what I'm thinking about :
apiVersion: v1 kind: Service metadata: name: my-service-01 namespace: myservices labels: k2c-singletags: mytag_secondtag foo: bar cluster: acme spec: [...]
It's also possible to add a "flag" label that would enable/disable this feature to optimize perfs
Thanks !
The text was updated successfully, but these errors were encountered:
Hello,
This is a good idea, we were actually thinking about doing this! I'll look into it.
Sorry, something went wrong.
No branches or pull requests
Hi !
Since Annotations are not available in Endpoints metadata, I suggest using only label for this case.
This is 2 kinds of possible consul tags :
mytag
secondtag
...foo=bar
cluster=acme
...kube2consul should support both :)
I made a very quick-and-dirty working proof of concept here : https://github.com/BarthV/kube2consul/tree/using-labels
This is what I'm thinking about :
It's also possible to add a "flag" label that would enable/disable this feature to optimize perfs
Thanks !
The text was updated successfully, but these errors were encountered: