Restructure and group userCRDs values files

[anders-elastisys]

Warning

This is a public repository, ensure not to disclose:

• personal data beyond what is necessary for interacting with this pull request, nor
• business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

• kind/feature
• kind/improvement
• kind/deprecation
• kind/documentation
• kind/clean-up
• kind/bug
• kind/other

Optional: Mark one or more of the following that are applicable:

Important

Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

• kind/admin-change
• kind/dev-change
• kind/security
• kind/adr

What does this PR do / why do we need this PR?

When looking at adding a new "self-managed service", I noticed that the values files that needed to be configured were quite spread out, making it a bit of a hassle to configure. This PR tries to address this somewhat by grouping all values files related to configuring userCRDs into one Helmfile values folder.

The user-crds chart was renamed to user-rbac-generator since it can be used to create any RBAC not necessarily tied to CRDs. There is also the possibility to configure extra RBAC for Application Developers.

This also adds missing values file for kafka and fixes the templating for creating the user-crds ClusterRoleBinding so that it is only created when there are resourceNames specified.

• Fixes #

Information to reviewers

There might be more improvements we would want to do, like adding a separate Helmfile label for grouping the RBAC and gatekeeper constraints needed for userCRDs. Also, the userCRDs name should maybe be changed to e.g. selfManagedServices or similar, as it is not necessary only related to CRDs, as it involves RBAC as well.

Checklist

• Proper commit message prefix on all commits
• Change checks:
  • The change is transparent
  • The change is disruptive
  • The change requires no migration steps
  • The change requires migration steps
  • The change upgrades CRDs
  • The change updates the config and the schema
• Documentation checks:
  • The public documentation required no updates
  • The public documentation required an update - [link to change](set-me)
• Metrics checks:
  • The metrics are still exposed and present in Grafana after the change
  • The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
  • The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)
• Logs checks:
  • The logs do not show any errors after the change
• Pod Security Policy checks:
  • Any changed pod is covered by Pod Security Admission
  • Any changed pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any pods to be blocked by Pod Security Admission or Policies
• Network Policy checks:
  • Any changed pod is covered by Network Policies
  • The change does not cause any dropped packets in the NetworkPolicy Dashboard
• Audit checks:
  • The change does not cause any unnecessary Kubernetes audit events
  • The change requires changes to Kubernetes audit policy
• Falco checks:
  • The change does not cause any alerts to be generated by Falco
• Bug checks:
  • The bug fix is covered by regression tests