You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As this chart generates the files for both the Operator and the Keycloak itself, it'd be a great feature to be able to disable one or the other to increase flexibility.
Describe the solution you'd like
Same as we have now {{- if .Values.keycloak.enabled }}, we could include something like {{- if .Values.operator.enabled }} in every operator template (deployment, service...).
Additional context
In our company, we want to have different projects, one for deploying the operator and another one for deploying Keycloak.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As this chart generates the files for both the Operator and the Keycloak itself, it'd be a great feature to be able to disable one or the other to increase flexibility.
Describe the solution you'd like
Same as we have now
{{- if .Values.keycloak.enabled }}
, we could include something like{{- if .Values.operator.enabled }}
in every operator template (deployment, service...).Additional context
In our company, we want to have different projects, one for deploying the operator and another one for deploying Keycloak.
The text was updated successfully, but these errors were encountered: