Allow to specify secrets labels and annotations from keycloakclient about keycloak-operator

[sathieu]

@vmuzikar Could you please review my proposal? We can start implementing it once you validate the proposed CRD schema.

[tomhuang12]

I would like this feature as well.

[tomhuang12]

An alternative method until the PR is merged is using Kyverno to add labels: https://kyverno.io/policies/other/add_labels/add_labels/

[andreaTP]

@tomhuang12 would you like to contribute to this feature?
Or, would you mind quickly summarizing how to use "Kyverno" as a workaround?
Thanks in advance!

[tomhuang12]

The policy looks something like this:

apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: add-keycloak-client-secret-kubed-annotations-example
spec:
  rules:
  - name: add-annotations
    match:
      any:
      - resources:
          kinds:
          - Secret
          namespaces:
          - keycloak
          names:
          - keycloak-client-secret-example
    mutate:
      patchStrategicMerge:
        metadata:
          annotations:
            kubed.appscode.com/sync: "kubernetes.io/metadata.name=example"

[stianst]

Thanks (again) for reporting this issue. Keycloak 19 was the last version that included this legacy Operator, and with the release of Keycloak 20 the Operator reached EOL and this repository will be archived, please see our blog post on this topic. If this issue is still valid for the Realm Operator, please re-open it there. Thanks for your understanding. And be sure to check out our new Operator!