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.
Currently it is rather cumbersome to configure KES in the tenant helm chart, because the entire section of values is commented in the values.yaml.
Describe the solution you'd like
The templates check of the configuration field is set to a value to render the kes section in the tenant CR, so every other value in the kes section would not need to be commented out. So my proposal is: comment out only the configuration key.
Describe alternatives you've considered
An alternative would be to introduce an explicit enabled field and uncomment everything.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently it is rather cumbersome to configure KES in the tenant helm chart, because the entire section of values is commented in the
values.yaml
.Describe the solution you'd like
The templates check of the configuration field is set to a value to render the kes section in the tenant CR, so every other value in the kes section would not need to be commented out. So my proposal is: comment out only the configuration key.
Describe alternatives you've considered
An alternative would be to introduce an explicit enabled field and uncomment everything.
The text was updated successfully, but these errors were encountered: