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
{{ message }}
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
Describe the bug
When a certificate is rotated, other QuarksSecrets that depend on it are not automatically rotated. This means that it is quite possible users will not be able to verify the dependent certificates.
To Reproduce
Apply the following resources (here in namespace kubecf, but that doesn't really matter):
The dependent certificate is rotated, so that it is signed by the new CA certificate. (Or I guess we could keep the private keys and just update the certificate, it doesn't really matter.)
Actual behaviour
The CA certificate is rotated.
The dependent certificate is not rotated; its .ca field no longer matches the CA certificate.
Environment
quarks-secret version v1.0.712
quarks-operatorv6.0.4-0.gb44bb859
quarks-jobv1.0.190
The text was updated successfully, but these errors were encountered:
Describe the bug
When a certificate is rotated, other QuarksSecrets that depend on it are not automatically rotated. This means that it is quite possible users will not be able to verify the dependent certificates.
To Reproduce
kubecf
, but that doesn't really matter):var-log-cache-ca.yaml
var-log-cache.yaml
rotate.log-cache-ca.yaml
Expected behaviour
Actual behaviour
.ca
field no longer matches the CA certificate.Environment
quarks-secret
versionv1.0.712
quarks-operator
v6.0.4-0.gb44bb859
quarks-job
v1.0.190
The text was updated successfully, but these errors were encountered: