Improvements:
- Use the endpoint IP address when generating a service id for NodePort services to prevent possible overlap of what are supposed to be unique ids
Bug fixes:
- Exclude Kubernetes system namespaces from Connect injection
Improvements:
- Use service's namespace when registering endpoints
- Update the Coalesce method to pass go vet tests
- Register Connect services along with the proxy. This allows the services to appear in the intention dropdown in the UI.[GH 77]
- Add
-log-level
CLI flag for catalog sync
Improvements:
- Add support for prepared queries in the Connect upstream annotation
- Add a health endpoint to the catalog sync process that can be used for Kubernetes health and readiness checks
Improvements:
- Clarify the format of the
consul-write-interval
flag forconsul-k8s
[GH 61] - Add datacenter support to inject annotation
- Update connect injector logging to remove healthcheck log spam and make important messages more visible
Bug fixes:
- Fix service registration naming when using Connect [GH 36]
- Fix catalog sync so that agents don't incorrectly deregister Kubernetes services [GH 40][GH 59]
- Fix performance issue for the k8s -> Consul catalog sync [GH 60]
Improvements:
- Supports a configurable tag for the k8s -> Consul sync [GH 42]
Bug fixes:
- Register NodePort services with the node's ip address [GH 8]
- Add the metadata/annotations field if needed before patching annotations [GH 20]
Improvements:
- Support syncing ClusterIP services [GH 4]
Bug fixes:
- Allow unnamed container ports to be used in connect-inject default annotations.
Bug fixes:
- Fix single direction catalog sync [GH 7]
Features:
- New subcommand:
inject-connect
runs a mutating admission webhook for automatic Connect sidecar injection in Kubernetes. While this can be setup manually, we recommend using the Consul helm chart.
- Initial release