Skip to content
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

update changelog for health checks #390

Merged
merged 5 commits into from
Nov 11, 2020
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,25 @@
## UNRELEASED

FEATURES:
* Connect: Support Kubernetes health probe synchronization with Consul for connect injected pods. [[GH-363](https://github.com/hashicorp/consul-k8s/pull/363)]
* Adds a new controller to the connect-inject webhook which is responsible for synchronizing Kubernetes pod health checks with Consul service instance health checks.
A Consul health check is registered for each connect-injected pod which mirrors the pod's Readiness status to Consul. This modifies connect routing to only
pods which have passing Kubernetes health checks. See breaking changes for more information.
* Adds a new label to connect-injected pods which mirror the `consul.hashicorp.com/connect-inject-status` annotation.
kschoche marked this conversation as resolved.
Show resolved Hide resolved
Consul-ENT only: Adds a new annotation to connect-injected pods when namespaces are enabled: `consul.hashicorp.com/consul-namespace` [[GH-376](https://github.com/hashicorp/consul-k8s/pull/376)]

BREAKING CHANGES:
* Connect: With the addition of the connect-inject health checks controller any connect services which have failing Kubernetes readiness
probes will no longer be routable through connect until their Kubernetes health probes are passing.
Previously, if any connect services were failing their Kubernetes readiness checks they were still routable through connect.
Users should verify that their connect services are passing Kubernetes readiness probes prior to using health checks synchronization.

DEPRECATIONS:
* `create-inject-token` in the server-acl-init job has been undeprecated.
kschoche marked this conversation as resolved.
Show resolved Hide resolved
`create-inject-auth-method` has been deprecated and replaced by `create-inject-token`.
kschoche marked this conversation as resolved.
Show resolved Hide resolved
`create-inject-namespace-token` in the server-acl-init job has been deprecated. [[GH-665](https://github.com/hashicorp/consul-helm/pull/665)].
kschoche marked this conversation as resolved.
Show resolved Hide resolved
See: [[GH-368](https://github.com/hashicorp/consul-k8s/pull/368)] for additional documentation regarding these changes.
ishustava marked this conversation as resolved.
Show resolved Hide resolved

IMPROVEMENTS:
* Connect: support passing extra arguments to the envoy binary. [[GH-378](https://github.com/hashicorp/consul-k8s/pull/378)]
Arguments can be passed in 2 ways:
Expand Down