Skip to content

Commit c22b7d0

Browse files
committed
docs(backups): state when the gate compares endpoints in the values reference
The values reference read as if the credentials endpoint were always compared and an object without the endpoint annotation never forced a render. Operators sizing the force counter or choosing a custom systemSecretName need both conditions spelled out. Assisted-by: LLM Signed-off-by: Alexey Artamonov <[email protected]>
1 parent 41c9ba1 commit c22b7d0

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

‎packages/system/backupstrategy-controller/values.yaml‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,10 +164,12 @@ backupStorage:
164164
# cozy-default routes to exists and forces THIS release when any is
165165
# missing. It repairs a stale S3 endpoint the same way: when the
166166
# credentials Secret's endpoint differs from the COSI Secret it is rendered
167-
# from it forces the bucket's <bucket>-system release, and when the
167+
# from it forces the bucket's <bucket>-system release (only while
168+
# systemSecretName is bucket-<bucketName>-system-credentials, the one
169+
# Secret that release renders), and when the
168170
# backups.cozystack.io/endpoint annotation on the Velero BSL or a default
169-
# Strategy differs from the credentials Secret's endpoint it forces THIS
170-
# release. The COSI Secret itself keeps the endpoint it was granted with, so
171+
# Strategy differs from the credentials Secret's endpoint, or is absent, it
172+
# forces THIS release. The COSI Secret itself keeps the endpoint it was granted with, so
171173
# after a publishing.host change that endpoint follows only once the
172174
# BucketAccess is re-granted. Both are throttled, independently, and a no-op
173175
# in the steady state. A suspended release is skipped rather than

0 commit comments

Comments
 (0)