A bit of a more invasive PR, so might need to work or end up rejected if it doesn't fit the idea you had, but it work on my projects
I basically added a kind value that switches between a DaemonSet and Deployment so I do not have to duplicate everything for a DaemonSet (kind of like ingress-nginx does), unfortunately that means i had to rename some values, which makes the values not backwards compatible.
I updated the labels to use cert-exporter.io/type: {{ kebabcase .Values.certManager.kind }} so I do not need separate sets for a DaemonSet and Deployment
Added a check to assert that the kind value is correct (certManager.assertValidKind)
The templated values before and after these changes still look the same:
A bit of a more invasive PR, so might need to work or end up rejected if it doesn't fit the idea you had, but it work on my projects
I basically added a
kind
value that switches between a DaemonSet and Deployment so I do not have to duplicate everything for a DaemonSet (kind of like ingress-nginx does), unfortunately that means i had to rename some values, which makes the values not backwards compatible.I updated the labels to use
cert-exporter.io/type: {{ kebabcase .Values.certManager.kind }}
so I do not need separate sets for a DaemonSet and DeploymentAdded a check to assert that the
kind
value is correct (certManager.assertValidKind
)The templated values before and after these changes still look the same: