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
It should be possible to deploy additional CAs with the autoTls backend.
If a company wants to use its own root certificate instead of the auto-generated one, an intermediate certificate can be given to the secret operator. Currently, the secret operator only provides this intermediate certificate in volume mounts. Tools, like kcat, which do not use this certificate as a trust anchor, additionally need the root certificate. Therefore, the SecretClass CRD should be extended to allow defining additional certificates, e.g.:
Description
It should be possible to deploy additional CAs with the autoTls backend.
If a company wants to use its own root certificate instead of the auto-generated one, an intermediate certificate can be given to the secret operator. Currently, the secret operator only provides this intermediate certificate in volume mounts. Tools, like kcat, which do not use this certificate as a trust anchor, additionally need the root certificate. Therefore, the SecretClass CRD should be extended to allow defining additional certificates, e.g.:
The text was updated successfully, but these errors were encountered: