Document how to configure KOTS for a GitOps workflow

[mrsimonemms]

GitOps is a regular feature request. This is supported out of the box with KOTS (docs), but need documentation on our website.

Things to consider:

• this will not be a repo where EVERYTHING is generated - this will still have an Installer job that generates the Gitpod YAML and installs at deploytime (see https://github.com/replicated-collab/replicated-gitpod/issues/8)
• it is worth ensuring that any secrets created as part of the gitpod-installer-job have the data obfuscated (example). It might be possible to create the secret as part of KOTS and then reference that secret in the job.
• KOTS supports SealedSecrets (docs) in alpha state. What limitations are there due to its status - is it reliable enough for our customers to use? This will be a question for Replicated to answer

Action items:

• Have a kick-off conversation with @lucasvaltl to ensure we're capturing all (known) customer requirements
• Set-up a Gitpod installation with GitOps
• Destroy the cluster and re-install Gitpod on a new cluster with GitOps → Does it solve Epic: [Self-Hosted] Enable a way to persist Gitpod K8s Manifests for Disaster recovery Purposes #10719?
• Try sealed secrets
• Write docs for our website

[mrsimonemms]

My first repo

[mrsimonemms]

For the moment, this ticket is out of scope. @lucasvaltl and I had a good discussion and concluded that this ticket is:

1. a documentation ticket
2. not actually solving any existing problems that any of our customers currently have

It is likely that this ticket will be done at some point, but it is not currently a pressing issue. GitOps is currently fully supported via the KOTS dashboard and enabled on all licenses so any user wishing to use it should see the Replicated documentation.

We will re-prioritise this ticket once we have paying customers with a need for this. To that end, we are re-opening #9926 because of paying customers having a need for it.

See internal discussion