ghp/ansible
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

cleanup and mass update: moving from Harbor to Gitea registries and from Drone to Gitea CI/CD with Gitea Act Runner

Browse Source
This commit is contained in:
ace
2023-06-10 06:20:10 +03:00
parent 1283a554fe
commit a251e593c6
89 changed files with 146 additions and 595 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
roles/harbor/defaults/main.yaml
View File

@ -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