Skip to content
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

Open
flozanorht opened this issue Jan 16, 2023 · 7 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@flozanorht
Copy link

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:

  • would container images from the internal registry be included in any of these backups?
  • would application data stored in S3 buckets be included?

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.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 17, 2023
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 17, 2023
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this as completed Jun 17, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jun 17, 2023

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

@flozanorht
Copy link
Author

/reopen

@flozanorht
Copy link
Author

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jun 19, 2023
@openshift-ci openshift-ci bot reopened this Jun 19, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jun 19, 2023

@flozanorht: Reopened this issue.

In response to this:

/reopen

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants