#TI CONNECT 1.6.1 COMPATIBILITTY UPGRADE#

#TI CONNECT 1.6.1 COMPATIBILITTY UPGRADE#

When performing a rolling upgrade and a version of Consul prior to 1.17.x is presented with a token created Consul v1.17.x or newer that contains templated policies, the templated policies field is not recognized. ACL tokens with templated policiesĪCL templated policies were added to 1.17.0 to simplify obtaining the right permissions for ACL tokens. Doing so ensures that no unexpected protocol changes occur during the upgrade. Service-defaults are configured in each partition and namespace before upgrading. If you are using non-default partitions and namespaces with Consul-k8s, we recommend explicitly defining these fields for all upstreams in addition to ensuring that accurate Now service-defaults configurations from the local partition and namespace are fetched when not specified in annotations. This bug is fixed starting in Consul v1.17.0. That did not explicitly specify a namespace or partition incorrectly used service-defaults configurations, such as default protocol, from the default partition and namespace instead of the local partition and namespace.

Prior to Consul v1.17.0, Kubernetes annotations for upstream services Service-defaults upstream config (Enterprise) Prior to Consul 1.17.0, audit logs contained timestamps on both the original log file names as well as rotated log file names.Īfter Consul 1.17.0, only timestamps will be included in rotated log file names. Consul 1.17.x Audit Log naming changes (Enterprise) This page is used to document those details separately from the standard Provided for their upgrades as a result of new features or changed behavior. However, specific versions of Consul may have more details The upgrading page covers the details of doing a

Ti connect 1.6.1 compatibilitty