Update k8s upgrade docs (#12123)
There is no longer the lifecycle sidecar
This commit is contained in:
parent
145703972a
commit
c785a5a0c5
|
@ -125,6 +125,7 @@ to update to the new version.
|
||||||
global:
|
global:
|
||||||
image: consul:1.8.3
|
image: consul:1.8.3
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
||||||
1. Determine your current installed chart version:
|
1. Determine your current installed chart version:
|
||||||
|
@ -220,9 +221,8 @@ the following will occur:
|
||||||
of time, however, it's important for the local Consul client to be restarted
|
of time, however, it's important for the local Consul client to be restarted
|
||||||
as quickly as possible.
|
as quickly as possible.
|
||||||
|
|
||||||
Once the local Consul client pod restarts, each service pod needs to re-register
|
Once the local Consul client pod restarts, each service pod needs to be re-registered
|
||||||
itself with the client. This is done automatically by the `consul-connect-lifecycle-sidecar`
|
with its local Consul client. This is done automatically by the connect inject controller.
|
||||||
sidecar container that is injected alongside each service.
|
|
||||||
|
|
||||||
Because service mesh pods are briefly deregistered during a Consul client restart,
|
Because service mesh pods are briefly deregistered during a Consul client restart,
|
||||||
it's **important that you do not restart all Consul clients at once**. Otherwise
|
it's **important that you do not restart all Consul clients at once**. Otherwise
|
||||||
|
|
Loading…
Reference in New Issue