Skip to content

[enterprise-4.18] OADP-5176: Support custom RBAC OADP to multi-tenancy #86752

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 7, 2025
Merged

[enterprise-4.18] OADP-5176: Support custom RBAC OADP to multi-tenancy #86752

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...nd_restore/application_backup_and_restore/installing/about-installing-oadp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
[id="about-installing-oadp"]
= About installing OADP
include::_attributes/common-attributes.adoc[]
include::_attributes/attributes-openshift-dedicated.adoc[]
:context: about-installing-oadp

toc::[]
Expand Down
14 changes: 6 additions & 8 deletions modules/about-installing-oadp-on-multiple-namespaces.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,16 +5,14 @@

:_mod-docs-content-type: CONCEPT
[id="about-installing-oadp-on-multiple-namespaces_{context}"]
= Installation of OADP on multiple namespaces
= Installation of {oadp-short} on multiple namespaces

You can install OpenShift API for Data Protection (OADP) into multiple namespaces on the same cluster so that multiple project owners can manage their own OADP instance. This use case has been validated with File System Backup (FSB) and Container Storage Interface (CSI).

You install each instance of OADP as specified by the per-platform procedures contained in this document with the following additional requirements:

* All deployments of OADP on the same cluster must be the same version, for example, 1.1.4. Installing different versions of OADP on the same cluster is *not* supported.
* Each individual deployment of OADP must have a unique set of credentials and at least one `BackupStorageLocation` configuration. You can also use multiple `BackupStorageLocation` configurations within the same namespace.
* By default, each OADP deployment has cluster-level access across namespaces. {product-title} administrators need to review security and RBAC settings carefully and make any necessary changes to them to ensure that each OADP instance has the correct permissions.
You can install {oadp-full} into multiple namespaces on the same cluster so that multiple project owners can manage their own {oadp-short} instance. This use case has been validated with File System Backup (FSB) and Container Storage Interface (CSI).

You install each instance of {oadp-short} as specified by the per-platform procedures contained in this document with the following additional requirements:

* All deployments of {oadp-short} on the same cluster must be the same version, for example, 1.4.0. Installing different versions of {oadp-short} on the same cluster is *not* supported.

* Each individual deployment of {oadp-short} must have a unique set of credentials and at least one `BackupStorageLocation` configuration. You can also use multiple `BackupStorageLocation` configurations within the same namespace.

* By default, each {oadp-short} deployment has cluster-level access across namespaces. {OCP} administrators need to carefully review potential impacts, such as not backing up and restoring to and from the same namespace concurrently.