From ed2db851d41782edded5f60aefb88611fcde9fe0 Mon Sep 17 00:00:00 2001 From: Nitya Dhanushkodi Date: Tue, 22 Feb 2022 11:31:11 -0800 Subject: [PATCH] Update changelog for multiport (#1041) --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 676cf4268d..29c5a0a9f7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,11 @@ FEATURES: a random UUID: `vault kv put secret/consul/replication key="$(uuidgen)"`. You will need to then provide this secret to both the primary and the secondary datacenters with `global.acls.replicationToken` values and allow the `global.secretsBackend.vault.manageSystemACLsRole` Vault role to read it. In the primary datacenter, the Helm chart will create the replication token in Consul using the UUID as the secret ID of the token. +* Connect: Support workaround for pods with multiple ports, by registering a Consul service and injecting an Envoy sidecar and init container per port. [[GH-1012](https://github.com/hashicorp/consul-k8s/pull/1012)] + * Transparent proxying, metrics, and metrics merging are not supported for multi-port pods. + * Multi-port pods should specify annotations in the format, such that the service names and port names correspond with each other in the specified order, i.e. `web` service is listening on `8080`, `web-admin` service is listening on `9090`. + * `consul.hashicorp.com/connect-service': 'web,web-admin` + * `consul.hashicorp.com/connect-service-port': '8080,9090` IMPROVEMENTS: * Helm