Skip to content

Docs: Caution to backup first before opting in

Thong Kuah requested to merge auto_devops_caution_postgres_channel into master

What does this MR do?

Caution to backup first before opting into version 2 of AUTO_DEVOPS_POSTGRES_CHANNEL

Related issues

Really want to avoid this scenario:

1. They have an existing deployment on Kubernetes 1.15.
2. Someone or themselves upgrades that cluster to Kubernetes 1.16
3. Their next Auto DevOps pipeline fails to deploy
4. They google around then follow the instructions in https://docs.gitlab.com/ee/topics/autodevops/#kubernetes-116
5. :boom: Their old postgresql DB is deleted, an empty new postgresql DB is created for them

See also https://gitlab.slack.com/archives/CP784K95Z/p1583961980205400 (internal slack thread)

A full upgrade guide is forthcoming in !26952 (merged)

Author's checklist

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖

Merge request reports