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 |
||
---|---|---|
.. | ||
bin | ||
monitoring/prometheus | ||
secrets | ||
certificates.yaml | ||
configmap-bin.yaml | ||
configmap-etc.yaml | ||
configmap-ingress-conf.yaml | ||
configmap-ingress-etc.yaml | ||
configmap-services-tcp.yaml | ||
cron-job-backup-mariadb.yaml | ||
deployment-error.yaml | ||
deployment-ingress.yaml | ||
job-image-repo-sync.yaml | ||
job-ks-user.yaml | ||
mariadb-backup-pvc.yaml | ||
network_policy.yaml | ||
pdb-mariadb.yaml | ||
pod-test.yaml | ||
secret-backup-restore.yaml | ||
secret-dbadmin-password.yaml | ||
secret-dbaudit-password.yaml | ||
secret-rgw.yaml | ||
secret-sst-password.yaml | ||
secrets-etc.yaml | ||
service-discovery.yaml | ||
service-error.yaml | ||
service-ingress.yaml | ||
service.yaml | ||
statefulset.yaml |