Browse Source

Doc added for Version specific upgrade Consul on Kubernetes components (#21101)

* Added upgrade instruction - NET-4882

* Update website/content/docs/k8s/upgrade/index.mdx

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>

* Update index.mdx

Fixed the link of grpc ports

---------

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
rboyer/deployer-with-v2-tproxy-bookmark
Sujata Roy 6 months ago committed by GitHub
parent
commit
943f0072c0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 2
      website/content/docs/k8s/upgrade/index.mdx

2
website/content/docs/k8s/upgrade/index.mdx

@ -15,6 +15,8 @@ As of Consul v1.14.0 and the corresponding Helm chart version v1.0.0, Kubernetes
The v1.0.0 release of the Consul on Kubernetes Helm chart also introduced a change to the [`externalServers[].hosts` parameter](/consul/docs/k8s/helm#v-externalservers-hosts). Previously, you were able to enter a provider lookup as a string in this field. Now, you must include `exec=` at the start of a string containing a provider lookup. Otherwise, the string is treated as a DNS name. Refer to the [`go-netaddrs`](https://github.com/hashicorp/go-netaddrs) library and command line tool for more information.
If you configured your Consul agents to use [`ports.grpc_tls`](https://developer.hashicorp.com/consul/docs/agent/config/config-files#grpc_tls_port) instead of [`ports.grpc`](https://developer.hashicorp.com/consul/docs/agent/config/config-files#grpc_port) and you want to upgrade a multi-datacenter deployment with Consul servers running outside of the Kubernetes cluster to v1.0.0 or higher, set [`externalServers.tlsServerName`](/consul/docs/k8s/helm#v-externalservers-tlsservername) to `server.<primary-datacenter>.domain`.
## Upgrade types
We recommend updating Consul on Kubernetes when:

Loading…
Cancel
Save