install-oadp

yesd4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4 { }

Updated Sep 4, 2025
One-click install
npx skills add https://github.com/mpryc/ai-agents-and-skills --skill install-oadp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-oadp
Source: https://github.com/mpryc/ai-agents-and-skills/tree/main/claude/oadp-operator/skills/operations/install-oadp
Command: npx skills add https://github.com/mpryc/ai-agents-and-skills --skill install-oadp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenShift clusters often require a reliable, repeatable process to install and configure the OpenShift API for Data Protection (OADP) operator and a DataProtectionApplication (DPA). It standardizes the setup across cloud providers and storage backends, reducing manual errors and ensuring backup readiness.

Core Features & Use Cases

  • Install OADP operator and create the openshift-adp namespace.
  • Configure cloud provider credentials and create a DataProtectionApplication.
  • Verify operator readiness, Velero components, and backup storage locations; supports AWS S3, Azure Blob, GCP Cloud Storage, MCG/NooBaa and Kopia-based data mover.
  • Use cases include fresh installations, cluster upgrades, provider migrations, and testing backup/restore workflows.

Quick Start

Begin by installing the OADP operator on your OpenShift cluster and creating a DPA manifest to verify backup readiness.

Frequently Asked Questions about install-oadp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the OADP operator and configure a DataProtectionApplication on OpenShift?

Install the OADP operator by creating the openshift-adp namespace, configuring cloud provider credentials, and deploying a DataProtectionApplication (DPA) manifest. The process coordinates namespace creation, credentials setup, DPA deployment, and verification steps to ensure backup readiness across your OpenShift clusters.

What cloud providers and storage backends are supported for OADP backup configurations?

OADP supports multi-provider configurations across AWS S3, Azure Blob, GCP Cloud Storage, and NooBaa/MCG backends. It also supports Kopia-based data mover configurations, allowing you to configure credentials and DataProtectionApplication manifests for various cloud storage providers.

Can I use OADP for both fresh OpenShift installations and cluster upgrades?

Yes, OADP covers fresh installations, cluster upgrades, and provider migrations on OpenShift clusters. The standardized setup reduces manual errors by coordinating namespace creation, credentials configuration, DPA deployment, and verification steps across different installation scenarios.

What is the best way to verify OADP operator readiness and backup storage locations?

Verify OADP readiness by checking operator status, Velero components, and backup storage locations after deploying your DataProtectionApplication. The verification process confirms backup readiness across configured AWS S3, Azure Blob, GCP Cloud Storage, or NooBaa/MCG storage backends.

Do I need to configure Kopia-based data mover separately when setting up OADP on OpenShift?

OADP supports Kopia-based data mover configurations as part of the DataProtectionApplication setup. You configure it alongside cloud provider credentials and storage backends, coordinating the setup through YAML manifests and sample configurations during the DPA deployment process.

Why does OADP standardize the backup installation process across different OpenShift clusters?

OADP standardizes backup setup to reduce manual errors and ensure reliable, repeatable backup readiness across OpenShift clusters. It provides consistent YAML manifests and sample configurations for namespace creation, credentials, and DPA deployment across AWS, Azure, GCP, and other backends.