feat(charts):[#375] Add example umbrella chart with multiple pre-conf…

…igured dataproviders

charts/connector/umbrella/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

charts/connector/umbrella/Chart.yaml

@@ -0,0 +1,34 @@
+apiVersion: v2
+name: umbrella
+description: A Helm chart for Kubernetes
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 0.1.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: "1.16.0"
+
+dependencies:
+  - name: tx-data-provider
+    alias: dataprovider
+    version: 0.0.1
+    repository: file://../test-provider
+  - name: tx-data-provider
+    alias: dataconsumer
+    version: 0.0.1
+    repository: file://../test-provider

charts/connector/umbrella/values.yaml

@@ -0,0 +1,126 @@
+dataconsumer:
+  fullnameOverride: dataconsumer
+  tractusx-connector:
+    fullnameOverride: dataconsumer-edc
+    participant:
+      id: BPNL00000001CRHK
+    controlplane:
+      ingresses:
+        - enabled: true
+          hostname: "dataconsumer-controlplane.test"
+          annotations:
+            nginx.ingress.kubernetes.io/ssl-passthrough: "false"
+            nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
+            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
+          endpoints:
+            - protocol
+            - management
+          tls:
+            enabled: true
+            secretName: tls-secret
+    dataplane:
+      ingresses:
+        - enabled: true
+          hostname: "dataconsumer-dataplane.test"
+          annotations:
+            nginx.ingress.kubernetes.io/ssl-passthrough: "false"
+            nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
+            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
+          endpoints:
+            - public
+          className: "nginx"
+          tls:
+            enabled: true
+            secretName: tls-secret
+    postgresql:
+      #      jdbcUrl: "jdbc:postgresql://dataconsumer-db-hl:5432/edc"
+      #      jdbcUrl: "jdbc:postgresql://dataconsumer-db:5432/edc"
+
+      #      jdbcUrl: "jdbc:postgresql://umbrella-postgresql-hl:5432/edc"
+      jdbcUrl: "jdbc:postgresql://umbrella-postgresql:5432/edc"
+
+  edc-postgresql:
+    fullnameOverride: dataconsumer-db
+
+  digital-twin-registry:
+    fullnameOverride: dataconsumer-digital-twin-registry
+    postgresql:
+      fullnameOverride: dataconsumer-digital-twin-registry-db
+    registry:
+      host: dataconsumer-digital-twin-registry.test
+
+  submodelservers:
+    fullnameOverride: dataconsumer-submodelserver
+    ingress:
+      enabled: true
+      hosts:
+        - host: dataconsumer-submodelserver.test
+          paths:
+            - path: /
+              pathType: ImplementationSpecific
+      tls:
+        - hosts:
+            - dataconsumer-submodelserver.test
+          secretName: tls-secret
+
+dataprovider:
+  fullnameOverride: dataprovider
+  tractusx-connector:
+    fullnameOverride: dataprovider-edc
+    participant:
+      id: BPNL00000001CRHK
+    controlplane:
+      ingresses:
+        - enabled: true
+          hostname: "dataprovider-controlplane.test"
+          annotations:
+            nginx.ingress.kubernetes.io/ssl-passthrough: "false"
+            nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
+            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
+          endpoints:
+            - protocol
+            - management
+          tls:
+            enabled: true
+            secretName: tls-secret
+    dataplane:
+      ingresses:
+        - enabled: true
+          hostname: "dataprovider-dataplane.test"
+          annotations:
+            nginx.ingress.kubernetes.io/ssl-passthrough: "false"
+            nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
+            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
+          endpoints:
+            - public
+          className: "nginx"
+          tls:
+            enabled: true
+            secretName: tls-secret
+    postgresql:
+      #      jdbcUrl: "jdbc:postgresql://dataprovider-db-hl:5432/edc"
+      jdbcUrl: "jdbc:postgresql://dataprovider-db:5432/edc"
+
+  edc-postgresql:
+    fullnameOverride: dataprovider-db
+
+  digital-twin-registry:
+    fullnameOverride: dataprovider-digital-twin-registry
+    postgresql:
+      fullnameOverride: dataprovider-digital-twin-registry-db
+    registry:
+      host: dataprovider-digital-twin-registry.test
+
+  submodelservers:
+    fullnameOverride: dataprovider-submodelserver
+    ingress:
+      enabled: true
+      hosts:
+        - host: dataprovider-submodelserver.test
+          paths:
+            - path: /
+              pathType: ImplementationSpecific
+      tls:
+        - hosts:
+            - dataprovider-submodelserver.test
+          secretName: tls-secret