Split containers into dedicated definitions

[sebastiangaiser]

Pyrra is currently deployed into a single Deployment resource with 2 containers:

• pyrra-kubernetes
• pyrra

It should be possible to scale them individually.
Migration plan:

1. Outsource the pod definition in the Deployment into a dedicated _pod.tpl with dedicated container templates.
2. Add dedicated Deployment files for each container using each dedicated container templates. This should be a using feature flag.

[sjentzsch]

@sebastiangaiser is that something I can help you with? We also have the demand for that at the moment. As we run separate observability stacks within the same cluster, I would like to deploy the operator-part + CRDs once, and separately one api/ui per observability stack (excl. CRDs). Meaning, this issue, and the possibility to disable CRDs would by my wish for the Helm chart. If that makes sense to you, I can file according PRs this week.

[sebastiangaiser]

Hey, the first step is already done. Feel free to open a PR for separating the Deployment resources.
I'm not sure if I understand what you want to do with the CRD. Helm provides the --skip-crds flag. This is also supported by GitOps tools like Flux. Would this work out for you?