Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-193

BSL with custom secret name and restic enabled causes containerCreating pods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • OADP 1.0.0
    • None
    • None
    • None
    • False
    • False
    • Passed
    • 0
    • 0
    • 0
    • Untriaged
    • None

      If a user sets the following DPA CR:

      ```
      apiVersion: oadp.openshift.io/v1alpha1
      kind: DataProtectionApplication
      metadata:
        name: velero-sample
      spec:
        configuration:
          velero:
            defaultPlugins:
            - openshift
            - aws
          restic:
            enable: true
        backupLocations:
          - velero:
              provider: aws
              default: true
              objectStorage:
                bucket: my-bucket-name
                prefix: velero
              config:
                region: us-east-1
                profile: "default"
              credential:
                name: custom-secret
                key: cloud

      ```

      Notice the custom-secret name, with restic enabled. The restic daemonset pods will be stuck in `containerCreating` state.

              rhn-engineering-dymurray Dylan Murray
              rhn-engineering-dymurray Dylan Murray
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: