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
This would replace the init container with the use of the Helm genSelfSignedCert function for simple certificate management.
#212 (and by extension #207) should also be considered for extended certificate management.
I propose the chart should work in three ways:
No certificate is generated. (this is the default: selfSignedCert.enabled=false)
Setting selfSignedCert.enabled=true uses the genSelfSignedCert function to create a new self-signed certificates instead of using the alpine/openssl container initJob.
Specifying a new existingSecret value in the Helm chart causes Zitadel to use externally-managed certificates. (i.e. created by cert-manager)
Version
No response
App version
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Describe your problem
Continuing discussion from #189 by @eliobischof's request.
Describe your ideal solution
This would replace the init container with the use of the Helm
genSelfSignedCert
function for simple certificate management.#212 (and by extension #207) should also be considered for extended certificate management.
I propose the chart should work in three ways:
selfSignedCert.enabled=false
)selfSignedCert.enabled=true
uses thegenSelfSignedCert
function to create a new self-signed certificates instead of using thealpine/openssl
container initJob.existingSecret
value in the Helm chart causes Zitadel to use externally-managed certificates. (i.e. created bycert-manager
)Version
No response
App version
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: