Commit 19c0abe5 authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'add_awareness_to_hubble_possible_failure' into 'master'

Add information into cilium documentation

See merge request gitlab-org/gitlab!64136
parents 342b05df e712b6ca
...@@ -463,7 +463,10 @@ Installation and removal of the Cilium requires a **manual** ...@@ -463,7 +463,10 @@ Installation and removal of the Cilium requires a **manual**
[restart](https://docs.cilium.io/en/stable/gettingstarted/k8s-install-gke/#restart-unmanaged-pods) [restart](https://docs.cilium.io/en/stable/gettingstarted/k8s-install-gke/#restart-unmanaged-pods)
of all affected pods in all namespaces to ensure that they are of all affected pods in all namespaces to ensure that they are
[managed](https://docs.cilium.io/en/v1.8/operations/troubleshooting/#ensure-managed-pod) [managed](https://docs.cilium.io/en/v1.8/operations/troubleshooting/#ensure-managed-pod)
by the correct networking plugin. by the correct networking plugin. Whenever Hubble is enabled, its related pod might require a
restart depending on whether it started prior to Cilium. For more information, see
[Failed Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#failed-deployment)
in the Kubernetes docs.
NOTE: NOTE:
Major upgrades might require additional setup steps. For more information, see Major upgrades might require additional setup steps. For more information, see
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment