-
Notifications
You must be signed in to change notification settings - Fork 62
K8SPG-553: Allow setting root CA manually #876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e2e-tests/functions
Outdated
kubectl create namespace cert-manager || : | ||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true || : | ||
kubectl apply -f "https://github.com/jetstack/cert-manager/releases/download/v${CERT_MANAGER_VER}/cert-manager.yaml" --validate=false || : 2>/dev/null | ||
if [ "$OPENSHIFT" == "4.10" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we do not support OPENSHIFT 4.10 long time ago
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the results of new test (custom-tls), we need to add it to csv files
// The secret containing the root CA certificate and key for | ||
// secure connections to the PostgreSQL server. It will need to contain the | ||
// CA TLS certificate and CA TLS key with the data keys set to | ||
// root.crt and root.key, respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't forget to have this in our docs as well I think. @fiowro
// RootCertSecret is the default root certificate secret name | ||
RootCertSecret = "pgo-root-cacert" /* #nosec */ | ||
// RootCertSecret = "pgo-root-cacert" /* #nosec */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why we commented it. Should we delete it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We comment unused crunchy code to simplify the merge process, as seen here:
percona-postgresql-operator/internal/controller/postgrescluster/pgbouncer.go
Lines 234 to 238 in 8910766
// K8SPG-330: Keep this commented in case of conflicts. | |
// We don't want to delete TLS secrets on cluster deletion. | |
// if err == nil { | |
// err = errors.WithStack(r.setControllerReference(cluster, intent)) | |
// } |
commit: 4db807a |
https://perconadev.atlassian.net/browse/K8SPG-553
https://perconadev.atlassian.net/browse/K8SPG-555
DESCRIPTION
K8SPG-555
: The operator will create a different ca secret per cluster with the name<cluster-name>-cluster-ca-cert
instead ofpgo-root-cacert
K8SPG-553
: Add a.spec.secrets.customRootCATLSSecret
field, which is used to specify data about the CA secret to be used by a cluster.CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
Config/Logging/Testability