-
Notifications
You must be signed in to change notification settings - Fork 20
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
PG-1244 Added a limitation about KMS configuration update #373
base: main
Are you sure you want to change the base?
Conversation
Performance test results:
|
@@ -24,6 +24,8 @@ Users can configure encryption differently for each database, encrypting specifi | |||
|
|||
* Keys in the local keyfile are stored unencrypted. | |||
* System tables are currently not encrypted. | |||
* When updating the Key Management Store (KMS) configuration, ensure that both PostgreSQL and the KMS are up and running. For example, if you update the URL for the KMS and PostgreSQL is offline during these changes, it will not be able to start. [Talk to our experts](https://www.percona.com/about/contact) to outline the best update path for you. |
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.
No, you currently can't update the configuration for an exisitng KMS, we do not have any functions to do that.
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.
Wait so https://perconadev.atlassian.net/browse/PG-1244 is not valid?
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.
It's valid, but the issue is bigger, Jan misunderstood part of the problem.
PG-1244
Description
Added a limitation about KMS configuration update