Value Statement

cert rotation should be a requirement for the on-premise environment. the admin can rotate the certs if needed so that it can mitigate the security risk. 

It depends on Centralized PostgreSQL. if it will leverage cruchy operator, we can leverage it directly. then verify and close this user story. 

Definition of Done for Engineering Story Owner (Checklist)

• use tls based authentication to connect to the postgres - refer to https://github.com/sclorg/postgresql-container/tree/master/examples/enable-ssl
• Provide a mechanism to rotate the certs
• support BYO with tls authentication

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.