feat: coroot - add custom initContainers

[MemberIT]

Add custom initContainers for coroot chart for fix permission error of data directory if set values of podSecurityContext and securityContext:

...
  podSecurityContext:
    fsGroup: 2000
  securityContext:
    capabilities:
      drop:
        - ALL
    readOnlyRootFilesystem: true
    runAsNonRoot: true
    runAsUser: 1000
...

For example init-chown init container:

  initContainers:
    - name: init-chown
      image: busybox
      securityContext:
        runAsNonRoot: false
        runAsUser: 0
      resources:
        limits:
          cpu: 100m
          memory: 128Mi
        requests:
          cpu: 50m
          memory: 64Mi
      command: ['sh']
      args:
        - "-c"
        - |
          set -ex
          chown 1000:2000 /data
      volumeMounts:
        - name: data
          mountPath: /data

[def]

@MemberIT, thanks for the PR!
BTW, running Coroot as a non-root user is already supported through our Kubernetes operator. You can find more details here: Coroot Kubernetes Installation.
Perhaps you might want to use it instead of plain Helm?

[MemberIT]

Thank you, @def, for providing the documentation link. However, at this time, deploying Coroot via the operator doesn’t suit our infrastructure needs (we only need one Coroot instance in our k8s cluster). Also, from what I can tell, the operator doesn’t allow us to carry over all the settings we have in our current chart—especially for the subcharts (ClickHouse and ZooKeeper).

I noticed that in the documentation, “Community Edition (Helm…” is marked as “deprecated)” Are you planning to discontinue further development of this deployment option (and focus solely on the operator)? Or do you perhaps need help in continuing the development of this option?

[def]

@MemberIT we’d love to support the Helm chart, but we’ve encountered some issues with it, such as the inability to resize PVs, as well as difficulties upgrading ClickHouse or Prometheus. Using an operator allows us to control each component more effectively, with direct access to the specs from code