Skip to content

Add GitOps secrets management page

Viktor Nagy (GitLab) requested to merge nagyv-gitlab-master-patch-59502 into master

What does this MR do and why?

Adds a page that describes how to do secret management with GitOps using the Sealed Secrets controller. I plan to add another page that shows how to use Helm and kustomize in a GitOps workflow.

The issue we face today is that Auto DevOps is great for beginner Kubernetes users, but it does not support a GitOps workflow, while experienced users prefer a GitOps workflow.

The agent enables to run GitOps workflows, but we don't have any guidelines for non-experts on how to get those workflows running.

I see at least 2-3 pages of content to provide the guidelines:

  • secrets management the GitOps way
  • access to containers stored in the GitLab registry
  • using Helm or kustomize with the agent
  • modifying Auto DevOps to use with the agent

The catch is that topic nr 2 "access to containers stored in the GitLab registry" builds on "secrets management the GitOps way". I added these two topics to this page, at the same time, there is no content on actually accessing a container.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Viktor Nagy (GitLab)

Merge request reports