rancher-backup

image:

repository: chainreg.biz/chainguard-private/backup-restore-operator-fips

tag: 11.0.3-r0@sha256:517cdbfc4d100c6d18df8c2d2c08e2e7ec409e690a167272aa2419ad0f323c2e

optionalResources:

## If enabled, will include kubewarden-related resources in the backups

kubewarden:

enabled: false

## Default s3 bucket for storing all backup files created by the backup-restore-operator

s3:

enabled: false

## credentialSecretName if set, should be the name of the Secret containing AWS credentials.

## To use IAM Role, don't set this field

credentialSecretName: ""

credentialSecretNamespace: ""

region: ""

bucketName: ""

folder: ""

endpoint: ""

endpointCA: ""

insecureTLSSkipVerify: false

## Optional s3 client configuration

# clientConfig:

# aws:

# ## Use dualstack endpoints (IPv6 support); defaults to true

# dualStack: false

# ## Bucket lookup mode: "auto", "dns" (virtual hosted style), or "path" (path style); defaults to "auto"

# bucketLookup: "dns"

## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

## If persistence is enabled, operator will create a PVC with mountPath /var/lib/backups

persistence:

enabled: false

## If defined, storageClassName: <storageClass>

## If set to "-", storageClassName: "", which disables dynamic provisioning

## If undefined (the default) or set to null, no storageClassName spec is

## set, choosing the default provisioner. (gp2 on AWS, standard on

## GKE, AWS & OpenStack).

## Refer https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1

##

storageClass: "-"

## If you want to disable dynamic provisioning by setting storageClass to "-" above,

## and want to target a particular PV, provide name of the target volume

volumeName: ""

## Only certain StorageClasses allow resizing PVs; Refer https://kubernetes.io/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/

size: 2Gi

# Add log level flags to backup-restore

debug: false

trace: false

# http[s] proxy server passed to backup client

# proxy: http://<username>@<password>:<url>:<port>

# comma separated list of domains or ip addresses that will not use the proxy

noProxy: 127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local

global:

cattle:

systemDefaultRegistry: ""

psp:

enabled: false # PSP enablement should default to false

kubectl:

repository: chainreg.biz/chainguard-private/kubectl-fips

tag: 1.36.5-r0@sha256:f7ca989b972e453b5e0fb36cda547e6d99d5c05b10b9343ac60abc415421b769

## Node labels for pod assignment

## Ref: https://kubernetes.io/docs/user-guide/node-selection/

##

nodeSelector: {}

## List of node taints to tolerate (requires Kubernetes >= 1.6)

tolerations: []

affinity: {}

serviceAccount:

annotations: {}

priorityClassName: ""

# Override imagePullPolicy for image

# options: Always, Never, IfNotPresent

# Defaults to Always

imagePullPolicy: "Always"

## Optional array of imagePullSecrets containing private registry credentials

## Ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

imagePullSecrets: []

monitoring:

metrics:

enabled: false

rancherBackupDurationBuckets: 0.5, 1, 2.5, 5, 7.5, 10, 30, 60, 120

serviceMonitor:

enabled: false

additionalLabels: {}

metricRelabelings: []

relabelings: []

prometheusRules:

## The "BackupFailed" alert is included by default when .Values.monitoring.prometheusRules.defaultAlert.enabled is set to true and rancher-monitoring is installed.

defaultAlert:

enabled: false

labels:

severity: critical

window: 5m

## Define custom Prometheus rules here.

customRules:

enabled: false

rules: []

securityContext:

## When persisting backup files to a PVC of type HostPath, set securityContext.runAsNonRoot to false.

## Only processes running as 'root' can write to HostPath PVCs so Backups will fail in that scenario if not running as 'root'.

## However, this goes against Kubernetes security best practices and should be avoided whenever possible.

runAsNonRoot: true

# Add resources for the backup-restore-operator container

resources: {}

# requests:

# cpu: 1

# memory: 1Gi

# limits:

# cpu: 2

# memory: 2Gi

# Extra annotations passed to the rancher-backup pods.

# extraAnnotations:

# new-annotation: "new-annotation-value"