cleanup and mass update: moving from Harbor to Gitea registries and from Drone to Gitea CI/CD with Gitea Act Runner
This commit is contained in:
@ -1,5 +1,6 @@
|
||||
harbor_enabled: true
|
||||
harbor_enabled: false
|
||||
harbor_publish: false
|
||||
harbor_chart_ref: "harbor/harbor"
|
||||
harbor_short_name: "harbor"
|
||||
harbor_use_external_db: true
|
||||
harbor_default_values:
|
||||
@ -48,12 +49,6 @@ harbor_default_values:
|
||||
subPath: ""
|
||||
accessMode: "{{ harbor_registry_storage_mode | default(harbor_storage_mode) | default('ReadWriteMany') }}"
|
||||
size: "{{ harbor_registry_size | default('100Gi') }}"
|
||||
chartmuseum:
|
||||
existingClaim: ""
|
||||
storageClass: "{{ harbor_charts_storage | default(harbor_storage) | default('nfs-ssd') }}"
|
||||
subPath: ""
|
||||
accessMode: "{{ harbor_charts_storage_mode | default(harbor_storage_mode) | default('ReadWriteMany') }}"
|
||||
size: "{{ harbor_charts_size | default('50Gi') }}"
|
||||
jobservice:
|
||||
jobLog:
|
||||
existingClaim: ""
|
||||
@ -86,9 +81,6 @@ harbor_default_values:
|
||||
|
||||
imagePullPolicy: IfNotPresent
|
||||
|
||||
# The update strategy for deployments with persistent volumes(jobservice, registry
|
||||
# and chartmuseum): "RollingUpdate" or "Recreate"
|
||||
# Set it as "Recreate" when "RWM" for volumes isn't supported
|
||||
updateStrategy:
|
||||
type: RollingUpdate
|
||||
|
||||
|
@ -12,7 +12,7 @@
|
||||
create_namespace: true
|
||||
release_namespace: "{{ harbor_namespace | default(namespace) }}"
|
||||
release_name: "{{ harbor_name | default('harbor') }}"
|
||||
chart_ref: "{{ harbor_chart | default('harbor/harbor') }}"
|
||||
chart_ref: "{{ harbor_chart_ref }}"
|
||||
chart_version: "{{ harbor_version | default(omit) }}"
|
||||
release_values: "{{ harbor_combined_values | from_yaml }}"
|
||||
wait: true
|
||||
|
Reference in New Issue
Block a user