add cloud deployment workflow for kerberos hub

.github/workflows/kind-cloud.yaml

@@ -0,0 +1,85 @@
+name: Deploy on Kubernetes
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: "0 0 * * *" # This will run the workflow every day at midnight UTC
+
+jobs:
+  deploy-kind:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        kind: [v0.21.0, v0.22.0, v0.23.0, v0.24.0]
+    steps:
+      - name: Create k8s Kind Cluster
+        uses: helm/kind-action@v1
+        with:
+          version: ${{ matrix.kind }}
+      - name: Print Kubernetes Version
+        run: |
+          kubectl version
+      - name: Test Kubernetes Cluster
+        run: |
+          kubectl get no
+          kubectl get pods -A -o wide
+          kubectl get sc
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      # - name: Install OpenEBS
+      #   run: |
+      #     kubectl apply -f https://openebs.github.io/charts/openebs-operator.yaml
+      #     echo "Sleeping for 60 seconds, give time for the operator to create the CRDs" && sleep 60
+      #     kubectl get sc
+      #     kubectl get po -A -o wide
+      # - name: Install Minio
+      #   id: install-minio
+      #   run: |
+      #     git clone --depth 1 --branch v6.0.1 https://github.com/minio/operator.git && kubectl apply -k operator/
+      #     kubectl apply -f minio-tenant-base.yaml
+      #     echo "Sleeping for 60 seconds, give time for the operator/tenant to create the CRDs" && sleep 60
+      #     kubectl get po -A -o wide
+      #     kubectl get po -A -o wide | grep myminio-pool-0-0 | awk '{print $3}' | grep -q '2/2' && echo "myminio-pool-0-0 pod is running with status 2/2" || (echo "myminio-pool-0-0 pod is not running with status 2/2" && exit 1)
+      # - name: Install MongoDB
+      #   id: install-mongodb
+      #   run: |
+      #     helm repo add bitnami https://charts.bitnami.com/bitnami
+      #     kubectl create namespace mongodb
+      #     helm install mongodb -n mongodb bitnami/mongodb --values ./mongodb-values.yaml
+      #     echo "Sleeping for 120 seconds, give time for the helm chart to create the pods" && sleep 120
+      #     kubectl get pods -A -o wide
+      #     kubectl get pods -A -o wide | grep mongodb | awk '{print $3}' | grep -q '1/1' && echo "mongodb pod is running with status 1/1" || (echo "mongodb pod is not running with status 1/1" && exit 1)
+      # - name: Install RabbitMQ
+      #   id: install-rabbitmq
+      #   run: |
+      #     helm repo add bitnami https://charts.bitnami.com/bitnami
+      #     kubectl create namespace rabbitmq
+      #     helm install rabbitmq -n rabbitmq bitnami/rabbitmq --values ./rabbitmq-values.yaml
+      #     echo "Sleeping for 60 seconds, give time for the helm chart to create the pods" && sleep 60
+      #     kubectl get pods -A -o wide
+      #     kubectl get pods -A -o wide | grep rabbitmq | awk '{print $3}' | grep -q '1/1' && echo "rabbitmq pod is running with status 1/1" || (echo "rabbitmq pod is not running with status 1/1" && exit 1)
+      # - name: Install Kerberos Vault
+      #   id: install-kerberos-vault
+      #   run: |
+      #     kubectl create namespace kerberos-vault
+      #     kubectl apply -f ./kerberos-vault-deployment.yaml -n kerberos-vault
+      #     echo "Sleeping for 30 seconds, give time for the helm chart to create the pods" && sleep 30
+      #     kubectl get pods -A -o wide
+      #     kubectl get pods -A -o wide | grep kerberos-vault | awk '{print $3}' | grep -q '1/1' && echo "kerberos-vault pod is running with status 1/1" || (echo "kerberos-vault pod is not running with status 1/1" && exit 1)
+      # - name: Install Kerberos Agent
+      #   id: install-kerberos-agent
+      #   run: |
+      #     kubectl apply -f ./kerberos-agent-deployment.yaml
+      #     echo "Sleeping for 30 seconds, give time for the helm chart to create the pods" && sleep 30
+      #     kubectl get pods -A -o wide
+      #     kubectl get pods -A -o wide | grep agent | awk '{print $3}' | grep -q '1/1' && echo "kerberos-agent pod is running with status 1/1" || (echo "kerberos-agent pod is not running with status 1/1" && exit 1)
+      - name: Install Kerberos Hub helm chart
+        id: install-kerberos-hub
+        run: |
+          helm repo add kerberos https://charts.kerberos.io
+          helm repo update
+          kubectl create namespace kerberos-hub
+          helm install hub kerberos/hub --values kerberos-hub-helm.yaml -n kerberos-hub --create-namespace
+          echo "Sleeping for 30 seconds, give time for the helm chart to create the pods" && sleep 30
+          kubectl get pods -A -o wide
+          kubectl get pods -A -o wide | grep kerberos-hub | awk '{print $3}' | grep -q '1/1' && echo "kerberos-hub pod is running with status 1/1" || (echo "kerberos-hub pod is not running with status 1/1" && exit 1)

kerberos-hub-helm.yaml

@@ -0,0 +1,541 @@
+# Default values for kerberoshub.
+# This is a YAML-formatted file.
+# Declare variables to be passed into your templates.
+
+###########################################################################
+# LICENSING information: you will a license to run Kerberos Hub.
+# ----
+# Get your license from support@kerberos.io
+#license: "---ENTER-YOUR-LICENSE-HERE---"
+# License for 8 cameras (for more cameras, please contact us for a private license)
+license: "L/+FAwEBB2xpY2Vuc2UB/4YAAQIBB1BheWxvYWQBCgABCVNpZ25hdHVyZQEKAAAA/gMv/4YB/gEk/80QAC1naXRsYWIuY29tL2tlcmJlcm9zLWlvL2xpY2Vuc2UvbW9kZWxzLkxpY2Vuc2X/gQMBAQdMaWNlbnNlAf+CAAEMAQJJZAH/hAABA0tleQEMAAEHQ29tcGFueQEMAAEHRXhwVGltZQEEAAEERGF5cwEEAAEHQ2FtZXJhcwEEAAEFU2l0ZXMBBAABBlZhdWx0cwEEAAEKTWVkaWFMaW1pdAEEAAEJUGVycGV0dWFsAQIAAQZBY3RpdmUBAgABCUlwQWRkcmVzcwEMAAAAGP+DAQEBCE9iamVjdElEAf+EAAEGARgAADv/gjgBDAAAAAAAAAAAAAAAAAILa2VyYmVyb3MuaW8B+p0p8FRT4AH8dzWT/gEQARABEAH8dzWT/gIBAAH+AgBjpoCE2/c3iq4Bf0T8WKYHZdLqDkoqRyFBQ/1ouWgx5NgWPErkVXSf9AMaaeSKpgYU3u4d+mYAKrv53CSGLpMYl7Vt1DfAa6prXHWJ2pF2GNIcS4wIseAK5ZAWlvZDq7DUz16LQupCrBxFPhYMlS9KqdvtJpIA7dbcewlhbyOR/fkCOOhiBBnWg/c2KuVKGWVbrs72y1QeeHBFzJ1yqvxiN5Y6gptPfskx00gnNUwIjlwyv+uvtEtsxNLfrHZmu0tm35cT21qZsN4bPOPc0TUEl1d1kIKrqsl3t4opno9SSDTGLFP0bWRyy4am8+0P5xqQ8r3YyoZ0rA4qA3OU57e0Znk++P2uv9sF430vvVH662mRwtAn8kfpk6b0yn4HkjMQo2CtTREKY0fVnSqgeCkPJXUdLqT0UyrmGtdjam0JObEO38XG8KODmbjBxdCnrSni3P4OSOW+KchxofDVHBBgsIQffU4O9hIDVoe+tWeVG/Q3eH2J9Obk1dVZ8z8mBQpZgIDv1cMoQCsL6D0H7a1YT+IdoshzMFO2jDW7kKB5poVkIpTlalAiG9RKyOvHOJmOrvchMcW1bKXIdswtyqLzKxbnVKVyZX1GEE9XbxM2do7lp3YuQmKbPgklf85AP0DGsAatxrGbXDA328vY3JTSgprQAo5QvTbN0OlKcveKOgA="
+licenseServer:
+  url: "https://license.kerberos.io/verify"
+  token: "214%ˆ#ddfsf@#3rfdsgl_)23sffeqasSwefDSFNBM" # do not change otherwise Kerberos Hub will not work.
+
+# Private Docker Registry: The registry secret is required if you have your Docker images behind a private registry.
+# By default it will pull from Docker hub (https://hub.docker.com/r/kerberos).
+#imagePullSecrets:
+#  - name: regcred
+
+# Environment: set to 'production', 'develop', 'demo', 'staging' or 'acceptance'.
+# Set to 'true' if this is a private deployment.
+environment: "production"
+
+# Set to 'true' if this is a private deployment.
+isPrivate: true
+
+# If you plan a migration or doing maintenance, you can enable readonly.
+# This will stop any write process to mongodb or any processing done in the Kerberos Hub pipeline.
+readOnly: false
+
+# Which network ingress you are using in your Kubernetes Cluster
+ingress: "nginx" # or "traefik"
+
+# A mongodb instance is required to store all the relevant metadata (this can be standalone or in a cluster).
+mongodb:
+  # MongoDB URI (for example for a SaaS service like MongoDB Atlas)
+  # If uri is set, the below properties are not used (host, adminDatabase, username, password)
+  #uri: "mongodb+srv://xx:xx@kerberos-hub.xxx.mongodb.net/?retryWrites=true&w=majority&appName=xxx"
+
+  # Self-hosted mongodb, you could also use the uri property above.
+  host: mongodb.mongodb
+  adminDatabase: admin
+  username: yourusername
+  password: "yourpassword"
+
+# A MQTT broker (vernemq or other like mosquitto) is used to have a bi-directional
+# communication between Kerberos Agents and Kerberos Hub.
+# we recommend to use vernemq (as part of this installation), but a stand-alone mosquitto broker is also possible.
+mqtt:
+  host: "mqtt.yourdomain.com" # this needs to be a public accessible DNS name (it's used to communicate between Kerberos Agents and Kerberos Hub)
+  port: "8443"
+  protocol: "wss"
+  username: "yourusername"
+  password: "yourpassword"
+  legacy:
+    host: ""
+    port: ""
+
+# We are using a pipeline that is orchestrated through Kafka topics or RabbitMQ queues
+# Events are send back and forth until the processing is done.
+queueProvider: "RABBITMQ" # or "KAFKA"
+queueName: "kcloud-event-queue" # This is the topic to which all events are send.
+
+# RabbitMQ can be installed in the same cluster using a helm chart, or you can
+# use a service on  cloud provider like AWS, GCP, Azure, etc.
+rabbitmq:
+  host: "rabbitmq.rabbitmq:5672" # can be internal dns name or external
+  #host: "amqps://b-xxx-xxx-xxx-xxx-xxx.mq.eu-central-1.amazonaws.com:5671"
+  username: "yourusername"
+  password: "yourpassword"
+  exchange: ""
+
+# If you already have a Kafka cluster you might use this instead of RabbitMQ.
+kafka:
+  broker: "kafka1.yourdomain.com:9094" # can be internal dns name or external
+  username: "yourusername"
+  password: "yourpassword"
+  mechanism: "PLAIN"
+  security: "SASL_PLAINTEXT"
+
+# For allowing WEBRTC a STUN and TURN server is required.
+# You might want to install coturn in a seperate VM.
+# -> https://help.hcltechsw.com/sametime/11.6/admin/turnserver_ubuntu.html
+turn:
+  host: "turn:turn.yourdomain.com:8443" # this needs to be a public accessible DNS name.
+  username: "username1"
+  password: "password1"
+
+# (optional) OpenAI integration, used for semantic search
+# Langchain is used to translate text to a filter on the media page
+openai:
+  enabled: false
+  apikey: "xxx"
+
+# We have a kerberos vault component installed which contains all the
+# recordings. Kerberos vault is queried to retrieve the recordings
+# from the appropriate provider.
+kerberosvault:
+  uri: "https://api.vault.yourdomain.com" # this needs to be a public accessible DNS name.
+  provider: "a-provider"
+  accesskey: "xxx"
+  secretkey: "xxx"
+
+  # Archiving is used when creating a task. The underlying recording of the task will be copied from its
+  # existing provider to the below archived provider. Seperate credentials are used, as it makes possible to
+  # specify another retention period.
+  archive:
+    provider: "an-archive-provider"
+    accesskey: "xxx"
+    secretkey: "xxx"
+  thumbnail:
+    provider: "a-thumbnail-provider"
+    accessKey: "xxx"
+    secretKey: "xxx"
+  sprite:
+    provider: "a-sprite-provider"
+    accessKey: "xxx"
+    secretKey: "xxx"
+
+email:
+  provider: "mailgun"
+  from: "support@yourdomain.com"
+  displayName: "yourdomain.com"
+  mailgun:
+    domain: "mg.yourdomain.com"
+    apikey: "xxxx"
+  smtp:
+    server: "smtp.yourdomain.com"
+    port: "465"
+    username: "yourusername"
+    password: "yourpassword"
+  templates:
+    welcome: "welcome"
+    welcomeTitle: "Welcome to Kerberos Hub"
+    activate: "activate"
+    activateTitle: "Wonderful! Your Kerberos Hub is now active"
+    forgot: "forgot"
+    forgotTitle: "Password reset Kerberos Hub. You forgot your password"
+    share: "share"
+    shareTitle: "[Action] You received a recording from Kerberos Hub"
+    detection: "detection"
+    disabled: "disabled"
+    highupload: "highupload"
+    device: "device"
+    alertTitle: "[Alert] Kerberos Hub detected something an event"
+    deviceTitle: "[Device] A Kerberos Agent's status has been changed"
+
+# Following are all the different deployments needed to make
+# Kerberos hub properly working.
+
+kerberoshub:
+  api:
+    repository: kerberos/hub-api
+    pullPolicy: IfNotPresent
+    tag: "1.0.1384326925"
+    replicas: 2
+    jwtSecret: "this-is-a-secret-please-change-to-random-string" # change to a random value, this is for generating JWT tokens.
+    schema: "https"
+    url: "api.yourdomain.com"
+    resources:
+      requests:
+        memory: 100Mi
+        cpu: 250m
+
+    # E-mail templates
+    #volumeMounts:
+    #  - name: custom-email-templates
+    #    mountPath: /mail
+    #volumes:
+    #  - name: custom-email-templates
+    #    persistentVolumeClaim:
+    #      claimName: custom-layout-claim
+
+    # When migrating to another url, this might help migrating.
+    #legacyUrl: "api.legacy.yourdomain.com"
+
+    # MFA issuer name
+    mfaIssuer: "Kerberos.io"
+
+    # Admin API's are made available for automation of Kerberos Hub.
+    # To access those API's (e.g. creation of owner users), an API key needs to be provided.
+    apiKey: "a-random-admin-api-key"
+
+    ## Certificates
+    tls:
+      - hosts:
+          - "api.yourdomain.com"
+        secretName: kerberoshub-api
+      #- hosts:
+      #    - "api.legacy.yourdomain.com"
+      #  secretName: kerberoshub-api-legacy
+      - hosts:
+          - "admin.api.yourdomain.com"
+        secretName: kerberoshub-admin
+    language: "english"
+    fallbackLanguage: "english"
+    # Legacy (reseller) it is possible to link to AWS S3 and IAM (however Kerberos Vault is now the recommended option).
+    # This is primarily used for creation of subscriptions, and not needed if you are using mainly Kerberos Vault.
+    aws:
+      region: "xxx"
+      bucket: "xxx"
+      accessKey: "xxx"
+      secretKey: "xxx"
+    stripe: # We use stripe for billing, so it's possible to resell Kerberos Hub if agreed.
+      privateKey: "xxx"
+    slack: # Slack is used in the api, to send logs to a specific Slack channel.
+      enabled: "true"
+      hook: "yourslackhook" # https://hooks.slack.com/services/T08Q2Q9V5/xxKT/JALxxAk26bHtuqTfZ
+      username: "Kerberos Hub" # The slack username
+    elasticsearch: # Logs of the kerberos hub will be send to an elastic search cluster.
+      enabled: "false"
+      protocol: "http"
+      host: "yourelasticsearchinstance.com"
+      port: "9200"
+      index: "kerberos-cloud"
+      username: ""
+      password: ""
+    sso: # OIDC settings for allowing SSO.
+      - domain: "uug.ai"
+        redirectUrl: "https://api.cloud.kerberos.io/sso/callback/uug.ai"
+        forceSSO: "false"
+        issuer: "https://xxx.eu.auth0.com/"
+        claimId: "email" # claim which is used to identify the user
+        clientId: "xxx"
+        clientSecret: "xxx"
+        clientVerificationId: "" # This is only required for SSO chaining.
+      - domain: "kerberos.io"
+        redirectUrl: "https://api.cloud.kerberos.io/sso/callback/kerberos.io"
+        forceSSO: "false"
+        issuer: "https://accounts.google.com"
+        claimId: "email" # claim which is used to identify the user
+        clientId: "xxx"
+        clientSecret: "xxx"
+        clientVerificationId: "" # This is only required for SSO chaining.
+  frontend:
+    repository: kerberos/hub-frontend
+    pullPolicy: IfNotPresent
+    tag: "1.0.1384325093"
+    replicas: 2
+    schema: "https"
+    url: "yourdomain.com"
+    resources:
+      requests:
+        memory: 50Mi
+        cpu: 50m
+
+    # The front-end but in read-only mode
+    #demoUrl: "demo.yourdomain.com"
+    # When migrating to another url, this might help migrating.
+    #legacyUrl: "legacy.yourdomain.com"
+
+    tls:
+      - hosts:
+          - "yourdomain.com"
+        secretName: kerberoshub
+        #- hosts:
+        #    - "legacy.yourdomain.com"
+        #  secretName: kerberoshub-legacy
+    #demoTls:
+    #  - hosts:
+    #      - "demo.yourdomain.com"
+    #    secretName: kerberoshub-demo
+    mixpanel: # We can keep track logging in Mixpanel as well
+      apikey: "xxx"
+    sentry: # We can trace errors in Sentry
+      url: "https://xxx@sentry.io/xxx"
+    stripe: # We use stripe for billing, so it's possible to resell Kerberos Hub if agreed.
+      publicKey: ""
+    googlemaps: # Google maps is used inside the application to visualise cameras and sites.
+      apikey: "xxxx"
+    zendesk: # We can use different support tools, for now we use Zendesk but others can be integrated
+      url: "yourdomain.zendesk.com"
+    posthog: # Posthog is used for auditing and user interaction logging
+      key: "xxx"
+      url: "https://posthog.domain.com"
+
+    # You can disable the Kerberos agent buttons, this make sense
+    # in a white-label setup, or where you are managing the Kerberos Agents for your customers.
+    hideAddAgent: "false"
+
+    # Multi tenancy (domains)
+    # By default the Kerberos Hub allows multi-tenancy through the concept
+    # of accounts and subaccounts. However through the concept of domains, you
+    # take it a step further. Within a domain, user accounts are unique, and are prefixed by a (domain\).
+    #multiTenant: true
+    #tenantBaseDomain: "yourdomain.com" # this would resolve in following sub domain "https://domain.kerberos.io"
+
+    # Page title (browser)
+    title: "Kerberos Hub - Video surveillance as it should be"
+
+    # You can style Kerberos hub as you wish.
+    # 1. we do the styling on our side and bake it in the Docker image (change the logo attribute to your company name)
+    # 2. you bring your own logo (set logo to 'custom'), and mount the css file and favicons.
+    # we will need to include your logo in the Docker image, so please reach out to us.
+    logo: "custom"
+    # Custom layout: override css
+    # By providing a style.css file in the custom folder
+    # this file will override any css styling.
+    #volumeMounts:
+    #  - name: custom-layout
+    #    mountPath: /usr/share/nginx/html/assets/custom
+    #  - name: custom-favicon
+    #    mountPath: /usr/share/nginx/html/assets/favicon
+    #volumes:
+    #  - name: custom-layout
+    #    persistentVolumeClaim:
+    #      claimName: custom-layout-claim
+    #  - name: custom-favicon
+    #    persistentVolumeClaim:
+    #      claimName: custom-favicon-claim
+
+    # By specifying the below environments variables, you can tweak the
+    # headings and paragraphs of Kerberos Hub front-end.
+    # Login page
+    loginDescription: ""
+    loginCopyright: ""
+    # Dashboard page
+    dashboardTitle: ""
+    dashboardSubTitle: ""
+    # Latest events page
+    latestEventsTitle: ""
+    latestEventsSubTitle: ""
+    # Livestream/view page
+    livestreamTitle: ""
+    livestreamSubTitle: ""
+    # Media page
+    mediaTitle: ""
+    mediaSubTitle: ""
+    # Optional - for custom page.
+    cpuUsageDescription: ""
+    framesPerSecondDescription: ""
+    mlaUtilizationDescription: ""
+    objectsDetectedDescription: ""
+
+    # You can add custom links to the navigation bar.
+    navigationLinkTitle1: ""
+    navigationLinkUrl1: ""
+    navigationLinkTitle2: ""
+    navigationLinkUrl2: ""
+    navigationLinkTitle3: ""
+    navigationLinkUrl3: ""
+    navigationLinkTitle4: ""
+    navigationLinkUrl4: ""
+    navigationLinkTitle5: ""
+    navigationLinkUrl5: ""
+
+  cleanup:
+    repository: kerberos/hub-cleanup
+    pullPolicy: IfNotPresent
+    tag: "1.0.6436406806"
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  monitordevice:
+    repository: kerberos/hub-monitor-device
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256190978"
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+    # E-mail templates
+    #volumeMounts:
+    #  - name: custom-email-templates
+    #    mountPath: /mail
+    #volumes:
+    #  - name: custom-email-templates
+    #    persistentVolumeClaim:
+    #      claimName: custom-layout-claim
+  reactivate:
+    repository: kerberos/hub-reactivate
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256184527"
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  forwarder:
+    enabled: false
+    #repository: kerberos/vault-forwarder
+    #pullPolicy: IfNotPresent
+    #tag: "1.0.2732389692"
+    #resources:
+    #  requests:
+    #    memory: 10Mi
+    #    cpu: 10m
+  # This proxy is legacy for the old agent, will be migrated in the new Hub API.
+  proxy:
+    repository: kerberos/vault-proxy
+    pullPolicy: IfNotPresent
+    tag: "1.0.2733724812"
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+
+kerberospipeline:
+  event:
+    repository: kerberos/pipe-event
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256042211"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  monitor:
+    repository: kerberos/pipe-monitor
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256044005"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  sequence:
+    repository: kerberos/pipe-sequence
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256054139"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  throttler:
+    repository: kerberos/pipe-throttler
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256059962"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  notify:
+    repository: kerberos/pipe-notify
+    pullPolicy: IfNotPresent
+    tag: "1.0.7225931612"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+    # E-mail templates
+    #volumeMounts:
+    #  - name: custom-email-templates
+    #    mountPath: /mail
+    #volumes:
+    #  - name: custom-email-templates
+    #    persistentVolumeClaim:
+    #      claimName: custom-layout-claim
+  notifyTest:
+    repository: kerberos/pipe-notify-test
+    pullPolicy: IfNotPresent
+    tag: "1.0.6256094666"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+    # E-mail templates
+    #volumeMounts:
+    #  - name: custom-email-templates
+    #    mountPath: /mail
+    #volumes:
+    #  - name: custom-email-templates
+    #    persistentVolumeClaim:
+    #      claimName: custom-layout-claim
+  analysis:
+    repository: kerberos/pipe-analysis
+    pullPolicy: IfNotPresent
+    tag: "1.0.6897439184"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  dominantColor:
+    repository: kerberos/pipe-dominantcolor
+    pullPolicy: IfNotPresent
+    tag: "1.0.6971463620"
+    replicas: 3
+    resources:
+      requests:
+        memory: 512Mi
+        cpu: 500m
+      limits:
+        memory: 2Gi
+        cpu: 1000m
+  thumbnail:
+    repository: kerberos/pipe-thumbnail
+    pullPolicy: IfNotPresent
+    tag: "1.0.6962799851"
+    replicas: 2
+    quality: "1" # 1 (best) - 31 (worst)
+    width: "600"
+    height: "-1"
+    kerberosvault:
+      enabled: false # If you want to use Kerberos Vault to store the thumbnails
+    resources:
+      requests:
+        memory: 512Mi
+        cpu: 500m
+      limits:
+        memory: 2Gi
+        cpu: 1000m
+  counting:
+    repository: kerberos/pipe-counting
+    pullPolicy: IfNotPresent
+    tag: "1.0.6251572994"
+    replicas: 1
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m
+  sprite:
+    enabled: false # Enable or disable the sprite generation 'true' or 'false
+    repository: kerberos/pipe-sprite
+    pullPolicy: IfNotPresent
+    tag: "1.0.7190736361"
+    replicas: 5
+    interval: "1" # Number of secondes between each thumbnail in the sprite
+    width: "240" # Should not be changed for the moment (hard coded in UI)
+    height: "135" # Should not be changed for the moment (hard coded in UI)
+    resources:
+      requests:
+        memory: 512Mi
+        cpu: 500m
+      limits:
+        memory: 2Gi
+        cpu: 1000m
+  export:
+    repository: kerberos/pipe-export
+    pullPolicy: IfNotPresent
+    tag: "1.0.6437127898"
+    replicas: 2
+    resources:
+      requests:
+        memory: 10Mi
+        cpu: 10m