mgob.yaml

# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# Note that two backup plans are provided as templates - they contain dummy values and should be changed before
# attempting to apply the chart to your cluster.
replicaCount: 1
image:
  repository: stefanprodan/mgob
  pullPolicy: IfNotPresent

  # We need edge to be able to use the "configMap.data[name].target.params", required to set the auth db.
  # When this is official, update to the proper stable release.
  #
  # @see https://github.com/stefanprodan/mgob/commit/b70e86b3acba8c82447a568cfcdd31fbd5ee3f7c
  tag: edge
service:
  name: mgob
  externalPort: 8090
  internalPort: 8090
selector:
  role: mongo-backup
resources:
  limits:
    cpu: 100m
    memory: 128Mi
  requests:
    cpu: 100m
    memory: 128Mi
storage:
  longTerm:
    accessMode: "ReadWriteOnce"
    storageClass: "standard" # Note: Use the storage class for your cloud provider.
    name: "mgob-storage"
    size: 10Gi
  tmp:
    accessMode: "ReadWriteOnce"
    storageClass: "standard" # Note: Use the storage class for your cloud provider.
    name: "mgob-tmp"
    size: 3Gi
configMap:
  name: "mgob-config"
  data:
    # Add each plan as per below.
    sugarizer-database.yml: |
      target:
        host: "mymongodb-mongodb-replicaset-0.mymongodb-mongodb-replicaset.default,mymongodb-mongodb-replicaset-1.mymongodb-mongodb-replicaset.default,mymongodb-mongodb-replicaset-2.mymongodb-mongodb-replicaset.default"
        port: 27017
        database: ""
      scheduler:
        cron: "0 0,6,12,18 */1 * *"
        retention: 14
        timeout: 60
      gcloud:
        bucket: "BucketName"
        keyFilePath: /secret/service-acc-secret/service-account.json
      s3:
        url: "https://s3.region.amazonaws.com"
        bucket: "BucketName"
        accessKey: "AccessKey"
        secretKey: "SecretKey"
        api: "S3v4"
      azure:
        containerName: "ContainerName"
        connectionString: "ConnectionString"
secret: # Will be mainly required for GCloud Storage
  - name: service-acc-secret
## You can either insert your secret values as part of helm values, or refer externally created secrets.
#- name: gcp-example-secret-name
#- name: gcp-example-secret-name-with-values
#  data:
#    service-account.json: |
#      {
#        "type": "service_account",
#        "project_id": "your-gcp-project-id",
#        "private_key_id": "12345678901234567890",
#        "private_key": "-----BEGIN PRIVATE KEY-----\n...........\n-----END PRIVATE KEY-----\n",
#        ...
#      }
env: {}
#- name: HTTPS_PROXY
#  value: "http://localhost:3128"