Update changelog for multiport (hashicorp#1041)

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