# Default values for data-dashboard.

# This is a YAML-formatted file.

# Declare variables to be passed into your templates.

# -- This will set the replicaset count more information can be found here: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/

replicaCount: 1

# -- This sets the container image more information can be found here: https://kubernetes.io/docs/concepts/containers/images/

image:

repository: ghcr.io/eclipse-edc/data-dashboard

tag: 0.4.0

pullPolicy: IfNotPresent

# -- This is for setting pull secrets if private images are used.

imagePullSecrets:

# -- This is to override the chart name.

nameOverride: ""

fullnameOverride: ""

# -- This is for setting Kubernetes Annotations to a Pod.

# For more information checkout: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/

podAnnotations: {}

# -- This is for setting Kubernetes Labels to a Pod.

# For more information checkout: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

podLabels: {}

podSecurityContext: {}

# fsGroup: 2000

securityContext: {}

# capabilities:

# drop:

# - ALL

# readOnlyRootFilesystem: true

# runAsNonRoot: true

# runAsUser: 1000

# -- This is for setting up a service more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/

service:

# -- This sets the service type more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types

type: ClusterIP

# -- This sets the ports more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/#field-spec-ports

port: 8080

# -- This block is for setting up the ingress for more information can be found here: https://kubernetes.io/docs/concepts/services-networking/ingress/

ingress:

# -- If enabled, an ingress resource is created.

enabled: false

className: ""

annotations: {}

# kubernetes.io/ingress.class: nginx

# kubernetes.io/tls-acme: "true"

hosts:

- host: chart-example.local

# -- The value of the first path is used to determine the base path of the dashboard.

paths:

- path: /

pathType: Prefix

tls: []

# - secretName: chart-example-tls

# hosts:

# - chart-example.local

basicAuth:

# -- If enabled: Basic username/password also need to be configured for dashboard access.

enabled: false

# -- (string) The username to set for auth

username:

# -- (string) The password to set for auth

password:

config:

# -- (string) Change the application title displayed in the header

appTitle: EDC Dashboard

# -- If enabled, the user can add new connectors to the dashboard, that are stored in the local storage.

enableUserConfig: false

# -- Health check interval for the currently selected connector in the dashboard.

healthCheckIntervalSeconds: 30

# -- Set the initial theme (for available values, see theme switcher in top right)

initialTheme:

# -- Configure the menu of the dashboard.

# 'routerPath' must match the path configured for this view in the angular router.

# 'divider' adds a dividing line below the menu item.

# Menu items with 'viewDescription' will appear in the home view with this description.

# Available material symbols can be found here: https://marella.github.io/material-symbols/demo/#rounded

menuItems:

- text: Home

materialSymbol: home_app_logo

routerPath: home

divider: true

- text: Catalog

materialSymbol: book_ribbon

routerPath: catalog

viewDescription: "In the catalog view you can browse datasets of other connectors. For each dataset you can run contract negotiations to consume the data afterwards. If the selected connector has a federated catalog, the available datasets of other participants will be displayed automatically. Otherwise, you can request the catalog of other connectors configured in the dashboard. At any time you can request the catalog of unknown connectors by requesting it manually."

- text: Assets

materialSymbol: deployed_code_update

routerPath: assets

viewDescription: "The asset view allows you to create, edit and delete the assets (datasets) in your connector. An asset represents any data that can be shared, for example static files, streaming data or API access. The dashboard only allows you to create assets with data types that your data plane(s) support."

- text: Policy Definitions

materialSymbol: policy

routerPath: policies

viewDescription: "The policy definitions view allows you to create, edit and delete policies. Policies are a generic way of defining a set of duties, rights, or obligations. EDC and DSP express policies with ODRL."

- text: Contract Definitions

materialSymbol: contract_edit

routerPath: contract-definitions

divider: true

viewDescription: "The contract definitions view allows you to create, edit and delete contract definitions. Contract definitions link assets and policies by declaring which policies apply to a set of assets. Contract definitions contain two types of policies: an access policy (who can see or discover the data contract offer) and a contract policy (the actual terms and conditions of data use once a contract has been agreed upon)."

- text: Contracts

materialSymbol: handshake

routerPath: contracts

viewDescription: "The contract view allows you to browse all contract negotiations that have been finished with an agreement. You can switch between providing and consuming contracts of the selected connector. For consuming contracts a transfer process can be started to receive the asset."

- text: Transfer History

materialSymbol: schedule_send

routerPath: transfer-history

viewDescription: "The transfer history view lets you browse and deprovision finished and ongoing transfer processes. You can switch between providing and consuming transfer processes of the selected connector."

# -- Default resource requests and limits

resources:

limits:

cpu: 150m

memory: 100Mi

ephemeral-storage: 10Mi

requests:

cpu:

memory:

ephemeral-storage: 10Mi

# -- This is to setup a liveness probe. More information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

livenessProbe: {}

# -- This is to setup a readiness probe. More information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

readinessProbe: {}

# -- This section is for setting up autoscaling more information can be found here: https://kubernetes.io/docs/concepts/workloads/autoscaling/

autoscaling:

enabled: false

minReplicas: 1

maxReplicas: 10

targetCPUUtilizationPercentage: 80

# targetMemoryUtilizationPercentage: 80

# -- Additional volumes on the output Deployment definition. Should be used for pre-configuring connectors in the dashboard.

volumes: []

# - name: foo

# secret:

# secretName: mysecret

# optional: false

# -- Additional volumeMounts on the output Deployment definition. Should be used to mount the connector configuration at '/app/config/edc-connector-config.json'.

volumeMounts: []

# - name: foo

# mountPath: "/etc/foo"

# readOnly: true

nodeSelector: {}

tolerations: []

affinity: {}