<!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> <!-- Type of issue --> <!-- Un-comment the line for the applicable doc issue type to add its label. Note that all text on that line is deleted upon issue creation. --> <!-- /label gitlab-ce~9444928 - Correction or clarification needed. --> <!-- /label gitlab-ce~9444929 - New doc needed to cover a new topic or use case. --> <!-- /label gitlab-ce~9444931 - Review a page or group of pages in order to plan and implement major improvements/rewrites. --> <!-- /label gitlab-ce~9444932 - Anything else. --> ### Problem to solve It does not appear to be currently documented that users are able to upgrade a Kubernetes cluster that is integrated with GitLab without causing any issues. Include the following detail as necessary: >What product or feature(s) affected? GitLab <> Kubernetes Cluster Integration >What docs or doc section affected? Include links or paths. - [GitLab Managed Apps](https://docs.gitlab.com/ee/user/clusters/applications.html) - [Kubernetes clusters](https://docs.gitlab.com/ee/user/project/clusters/) ### Proposal We should include a section within one or both of the aforementioned docs that informs users and customers that if they need to upgrade their cluster while it is integrated with GitLab, they can do so without an issue. ### Other links/references <!-- E.g. related GitLab issues/MRs --> ZD: https://gitlab.zendesk.com/agent/tickets/128775 (Internal)