-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
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
All creation of metadata and tags from k8s annotations #141
Conversation
@nicholasjackson I've taken #135 and
Please review. @ishustava can you review as well please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, the connect-service-tags attribute never actually made it into the docs. But, I think good to have the depreciation just in case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
…ired for service-resolver. Note: tests were passing as this data is set on the service
- add back support for the old tags annotation but mark as deprecated - add tests that check more of the template rendering - fix bug where the -default-protocol flag wasn't being used - clean up whitespace in rendered init container script
ae60cae
to
fa7ecc5
Compare
Adding one commit to #135 that:
Original PR description:
This PR is a roll up of previous PRs as I found a bug. The original code was not setting the tags and service metadata for the proxy. While the tests were passing for this as the test only searches for the existence of tags in the command. Since this data was present on the service config the test passed however for Consul L7 config tags and metadata need to be present on the proxy.
Content:
Add annotation to allow the configuration of service tags in Consul
consul.hashicorp.com/service-tags, value is a comma separated string of tags to add to the service
Add annotation to allow the configuration of service metadata in Consul service catalog
consul.hashicorp.com/service-meta- individual annotations are specified with the metadata key in the annotation name. Key is the name of the metadata key to store in the Consul service catalog. Value of the annotation is the value set against the metadata.
A test docker container for this branch can be found at nicholasjackson/consul-k8s-dev:beta
Fixes #112