-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[online] Issue in file rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc #54721
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
/lifecycle frozen |
@flozanorht: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Which section(s) is the issue in?
"Backup and recovery"
https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.html#backup-recovery_rosa-policy-process-security
What needs fixing?
The usage of the term "object store backup" is confusing, and the explanation "all Kubernetes objects like etcd" is not sufficient to make its meaning clear.
As an AWS user, I would assume "object store" means S3 service as the destination of the backups or it means the backup of cluster data that is stored in S3 buckets, such as container images from the internal registry.
It is not clear from the table of what, if anything, these backups include other than Kubernetes API resources (stored in etcd) and application data on Persistent Volumes. For example:
IMHO our docs should be sensitivite to the terms AWS customers would be used to, even of the meaning would be clar to skilled OpenShift customers. And the internal registry should be mentioned explicitly, as well as application data stored on S3, RDS, and any other AWS server that we do not back up.
The text was updated successfully, but these errors were encountered: