5db88a5fb4
Challenge: Now remote_ks_admin and remote_rgw_user are using for user labels of backup target openstack cloud. When the backup user doesn't exist and we can enable job_ks_user manifest. But job_ks_user uses .Vaules.secrets.identity.admin and mariadb, while secret-rgw and cron-job-backup-mariadb use .Values.secrets. identity.remote_ks_admin and remote_rgw_user. It requires to use same values for admin and remote_ks_admin, and for mariadb and remote_rgw_user. Seems it isbreaking values consistency. Suggestion: Now providing 2 kinds of backup - pvc and swift. "remote_" means the swift backup. In fact, mariadb chart has no case to access to keystone except swift backup. So we can remove remote_xx_* prefix and there is no confusion. Change-Id: Ib82120611659bd36bae35f2e90054642fb8ee31f
15 lines
558 B
YAML
15 lines
558 B
YAML
---
|
|
mariadb:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
|
|
- 0.1.2 mariadb security best practice fixes
|
|
- 0.1.3 Fix MariaDB backup script
|
|
- 0.1.4 Unpin images built with osh-images
|
|
- 0.1.5 Update to container image repo k8s.gcr.io
|
|
- 0.1.6 Change Issuer to ClusterIssuer
|
|
- 0.1.7 Revert - Change Issuer to ClusterIssuer
|
|
- 0.1.8 Change Issuer to ClusterIssuer with logic in place to support cert-manager versioning
|
|
- 0.1.9 Uplift Mariadb-ingress to 0.42.0
|
|
- 0.1.10 Rename mariadb backup identities
|
|
...
|