GitLab supplies various DevOps tools to manage and run CI pipelines and even production deployments.
This is most convenient when connecting GitLab to a Kubernetes cluster. GitLab can then self-provision pods as needed to launch CI runners, deploy applications, run red/green deployments, and so on.
Starting with GitLab 14.5, the preferred way of managing such Kubernetes clusters is with a GitOps approach using GitLab's Kuberentes agent called KAS.
This is a separate service which the Kubernetes cluster can poll to pull in information and infrastructure specifications from GitLab.
Other methods of managing a Kubernetes cluster have been deprecated in GitLab 14.5. and will thus be removed in future versions (https://gitlab.com/groups/gitlab-org/configure/-/epics/8).
The documentation for enabling KAS can be found at https://docs.gitlab.com/ee/administration/clusters/kas.html.
/app/data/gitlab.yml seems to have no effect in Cloudron.
It would be great if the Cloudron package could be modified to allow for a KAS to be started.