Skip to content

Support different cloud providers between BSL + VSL #117

Closed
Closed
Support different cloud providers between BSL + VSL#117
Labels
GA blockerRequired for GA releasekind/bugCategorizes issue or PR as related to a bug.operator-dev

Description

@dymurray
dymurray
opened on Jun 22, 2021

Today OADP requires that the same cloud provider is used for BSL+VSL. This is not desired, as someone may want to use AWS for a BSL and Azure for a VSL or vice versa.

There are a few things to fix here:

  • OADP operator should allow you to specify different provider details between BSL/VSL, rather than sharing the same cloud provider
  • Test OADP with GCP for backup storage and volume snapshots and identify bugs
  • Test OADP with Azure for backup storage and volume snapshots and identify bugs
  • Negative testing against azure/gcp configuration params

Activity

  1. dymurray
    added
    kind/bugCategorizes issue or PR as related to a bug.
    GA blockerRequired for GA release
    on Jun 22, 2021
  2. dymurray
    added
    operator-dev
    on Aug 11, 2021
  3. dymurray
    closed this as completedon Sep 28, 2021
  4. mpryc
    added a commit that references this issue on Nov 27, 2024

    Update manifests for the non-admin-backup openshift#117 - Queue infor…

    33dfec6
  5. openshift-merge-bot
    added a commit that references this issue on Nov 27, 2024

    Update manifests for the non-admin-backup #117 - Queue information (#…

    f77ffcd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    GA blockerRequired for GA releasekind/bugCategorizes issue or PR as related to a bug.operator-dev

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions