Skip to content

Add annotation to preserve old encryption key#310

Merged
Jorres merged 1 commit intomasterfrom
database-encryption-key-override
Feb 6, 2026
Merged

Add annotation to preserve old encryption key#310
Jorres merged 1 commit intomasterfrom
database-encryption-key-override

Conversation

@Jorres
Copy link
Contributor

@Jorres Jorres commented Jan 30, 2026

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the new behavior?

Allows to specify a new annotation on the Database: ydb.tech/encryption-key-storage-name that will accept a Storage name override. Useful when a Storage object needs to be migrated (e.g. dev-storage-bad-name -> storage-standard-name to standardize internal Service endpoints generated by operator), but if we simply change .spec.StorageClusterRef, operator would recalculate key ID and database won't launch on next startup.

Other information

@Jorres
Copy link
Contributor Author

Jorres commented Jan 30, 2026

Maybe, as an additional precaution, also save current storageNameRef in "status" and validate that it can also be changed if annotation is supplied

@Jorres Jorres merged commit 6b6da03 into master Feb 6, 2026
3 checks passed
@Jorres Jorres deleted the database-encryption-key-override branch February 6, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants