docs: Clarify that encryption should not be in reconciler pipeline
UpgradeImpact ============= Operators should verify that encryption is not enabled in their reconciler pipelines; having it enabled there may harm data durability. For more information, see https://launchpad.net/bugs/1910804 Change-Id: I1a1d78ed91d940ef0b4eba186dcafd714b4fb808 Closes-Bug: #1910804
This commit is contained in:
2 changed files with 9 additions and 2 deletions
@@ -781,8 +781,9 @@ encrypted.
Encryption has no impact on the `container-reconciler` service. The
`container-reconciler` uses an internal client to move objects between
different policy rings. The destination object has the same URL as the source
object and the object is moved without re-encryption.
different policy rings. The reconciler's pipeline *MUST NOT* have encryption
enabled. The destination object has the same URL as the source object and the
object is moved without re-encryption.
Considerations for developers
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.