[martingxx]

I really like that there is a focus on being able to deploy in k8s. Nice work!

However, some teams (ours) already run their own k8s clusters and would probably want to deploy gitlab in a namespace in there.

I hoped there would be simple example k8s manifests for doing this, but last time I checked I could only find helm charts. We don't use helm and don't want to use it.

If anyone knows some k8s manifests I can cut and paste to get started I'd appreciate it. Otherwise, it's going be be a job of creating it all myself, which right now is what's stopping us evaluating gitlab properly.

[mbell]

Helm charts are just templated k8s manifests, you can have it spit out the final manifest and use it manually.

[martingxx]

Thanks. Maybe I will try that.

[WarheadsSE]

:wave: I'm a maintainer of the GitLab helm chart. You can certainly use `helm template` to get the output of our chart, and then make use of `kubectl` without issue. We have several large customers using this pattern, and is expected as an option due Helm 2.x's Tiller component being problematic in compliance regulated industries.

We can certainly work on surfacing this better in our documentation :thumbsup:

[kennyGitLab]

GitLab product person here - Thanks for the suggestion! I think this issue (scheduled for our 12.6 release coming out next month) should help. https://gitlab.com/gitlab-org/gitlab/issues/27630

[kennyGitLab]

Whoops - I think you are suggesting deploying GitLab the application to your existing Kubernetes cluster. The issue, and highlight from the blog post, were about deploying your applications (in GitLab projects) to a Kubernetes cluster.

[martingxx]

Thanks for your reply.

Yes, I was talking about deploying to our existing cluster. Pretty much the only requirement for software that we run is that it must run in our cluster.

Ironically, it's often harder to deploy applications that offer their own k8s deployment approaches because they often have their own opinionated ways of using it that don't match our policies.

[base698]

In your deploy step you can just use kubectl and set the user and context with variables you've provided the job.