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
Hey, I am using the fulcio helm charts as a dependency in my current implementation. Encountered a limitation when trying to include additional volume mounts. The issue originated with a TLS issue when using keycloak as an OIDC provider, because it was signed by an internal CA. The current chart does not seem to provide a way to set a CA to use for TLS verification, which is essential for my use case.
Is this just something we missed in the implementation?
If we did not miss something we would make the following Proposal:
I suggest modifying the chart to include parameters for custom volume mounts. This can be achieved by adding fields to the values.yaml file and updating the deployment templates and README.md accordingly.
Potential code changes:
Include helm templating lines:
{{- if .Values.extraVolumeMounts }} {{- toYaml .Values.extraVolumeMounts | nindent 10 }}{{- end }}
Description
Hey, I am using the
fulcio helm charts
as a dependency in my current implementation. Encountered a limitation when trying to include additional volume mounts. The issue originated with a TLS issue when using keycloak as an OIDC provider, because it was signed by an internal CA. The current chart does not seem to provide a way to set a CA to use for TLS verification, which is essential for my use case.Is this just something we missed in the implementation?
If we did not miss something we would make the following Proposal:
I suggest modifying the chart to include parameters for
custom volume mounts
. This can be achieved by adding fields to thevalues.yaml
file and updating the deployment templates and README.md accordingly.Potential code changes:
Additonal resources:
The text was updated successfully, but these errors were encountered: