Velero passthrough

Package Merge Request

Package MR

big-bang/product/packages/velero!209 (merged)

For Issue

Closes (big-bang/product/packages/velero#145 (closed))

Upgrade Notices

This release of velero migrates the chart to the passthrough pattern.

Shifting values

Values that traditionally have been used to configure the Velero chart are now available under the upstream key. The following values are now under said key:

• image
• nameOverride
• fullnameOverride
• resources
• upgradeJobResources
• initContainers
• podSecurityContext
• containerSecurityContext
• metrics
• kubectl
• configuration
• nodeAgent

These are only the values from upstream that are configured differently by Big Bang. All other Velero values are removed since they are defaults.

Plugins

Previously, the plugins value was used to initialize the which plugins to install. However, converting to the passthrough pattern makes it so the deployment configuration cannot be edited therefore making the plugins value unusable. Instead, users should use Velero's initContainers value and define a plugin as shown below.

initContainers:
  - name: velero-plugin-for-aws
    image: registry1.dso.mil/ironbank/opensource/velero/velero-plugin-for-aws:v1.12.1
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins
        resources:
          requests:
            memory: 512Mi
            cpu: 100m
          limits:
            memory: 512Mi
            cpu: 100m
        securityContext:
         capabilities:
          drop:
            - ALL