[bitnami/harbor] Adds different credential fields for each database (#2536)

* Adds different credential fields for each database Signed-off-by: Johannes Schnatterer <johannes.schnatterer@cloudogu.com> * [bitnami/harbor] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>
2026-04-02 07:17:26 +08:00 · 2020-05-12 13:58:44 +02:00
parent 627b472b5d
commit e824720946
8 changed files with 173 additions and 42 deletions
--- a/bitnami/harbor/values.yaml
+++ b/bitnami/harbor/values.yaml
@@ -14,7 +14,7 @@
 coreImage:
  registry: docker.io
  repository: bitnami/harbor-core
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -38,7 +38,7 @@ coreImage:
 portalImage:
  registry: docker.io
  repository: bitnami/harbor-portal
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -62,7 +62,7 @@ portalImage:
 jobserviceImage:
  registry: docker.io
  repository: bitnami/harbor-jobservice
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -86,7 +86,7 @@ jobserviceImage:
 chartMuseumImage:
  registry: docker.io
  repository: bitnami/chartmuseum
-  tag: 0.12.0-debian-10-r43
+  tag: 0.12.0-debian-10-r46
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -110,7 +110,7 @@ chartMuseumImage:
 registryImage:
  registry: docker.io
  repository: bitnami/harbor-registry
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -134,7 +134,7 @@ registryImage:
 registryctlImage:
  registry: docker.io
  repository: bitnami/harbor-registryctl
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -158,7 +158,7 @@ registryctlImage:
 clairImage:
  registry: docker.io
  repository: bitnami/harbor-clair
-  tag: 1.10.2-debian-10-r34
+  tag: 1.10.2-debian-10-r39
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -182,7 +182,7 @@ clairImage:
 clairAdapterImage:
  registry: docker.io
  repository: bitnami/harbor-adapter-clair
-  tag: 1.0.2-debian-10-r28
+  tag: 1.0.2-debian-10-r32
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -206,7 +206,7 @@ clairAdapterImage:
 notaryServerImage:
  registry: docker.io
  repository: bitnami/harbor-notary-server
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r38
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -230,7 +230,7 @@ notaryServerImage:
 notarySignerImage:
  registry: docker.io
  repository: bitnami/harbor-notary-signer
-  tag: 1.10.2-debian-10-r33
+  tag: 1.10.2-debian-10-r37
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -254,7 +254,7 @@ notarySignerImage:
 nginxImage:
  registry: docker.io
  repository: bitnami/nginx
-  tag: 1.17.10-debian-10-r29
+  tag: 1.17.10-debian-10-r33
  ## Specify a imagePullPolicy
  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -822,11 +822,11 @@ core:
 jobservice:
  replicas: 1
  ## Update strategy - only really applicable for deployments with RWO PVs attached
-  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
-  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
+  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the 
+  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will 
  ## terminate the single previous pod, so that the new, incoming pod can attach to the PV
  updateStrategy:
-    type: RollingUpdate
+    type: RollingUpdate   
  maxJobWorkers: 10
  # The logger for jobs: "file", "database" or "stdout"
  jobLogger: file
@@ -892,11 +892,11 @@ jobservice:
 registry:
  replicas: 1
  ## Update strategy - only really applicable for deployments with RWO PVs attached
-  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
-  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
+  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the 
+  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will 
  ## terminate the single previous pod, so that the new, incoming pod can attach to the PV
  updateStrategy:
-    type: RollingUpdate
+    type: RollingUpdate   
  ## Harbor Registry parameters
  ##
  registry:
@@ -1004,11 +1004,11 @@ chartmuseum:

  replicas: 1
  ## Update strategy - only really applicable for deployments with RWO PVs attached
-  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
-  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
+  ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the 
+  ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will 
  ## terminate the single previous pod, so that the new, incoming pod can attach to the PV
  updateStrategy:
-    type: RollingUpdate
+    type: RollingUpdate 

  port: 8080

@@ -1354,7 +1354,22 @@ externalDatabase:
  ## coreDatabase:
  ## External database name for clair
  ## clairDatabase:
+  ## if not set, database.external.user is used
+  ## clairUsername: ""
+  ## if not set, database.external.user is used
+  ## clairPassword: ""
  ## External database name for notaryserver
  ## notaryServerDatabase:
-  ## External database name for notaryserver
+  ## notaryServerDatabase: "notary_server"
+  ## if not set, database.external.user is used
+  ## notaryServerUsername: ""
+  ## if not set, database.external.password is used
+  ## notaryServerPassword: ""
+  ## External database name for notarysigner
  ## notarySignerDatabase:
+  ## notarySignerDatabase: "notary_signer"
+  ## if not set, database.external.user is used
+  ## notarySignerUsername: ""
+  ## if not set, database.external.password is used
+  ## notarySignerPassword: ""
+