Open mkz100 opened 2 years ago
secret yaml names mismatch -
multi-tenancy-gitops-apps/apic/environments/single-cluster/config/kustomization.yaml:
2. The scripts and instructions create the secret file in a different name as shown below **ibm-entitlement-key-secret.yaml**
grep ibm-entitlement-key-secret.yaml * -r
multi-tenancy-gitops-apps/apic/environments/single-cluster/config/secrets/ibm-entitlement-key-secret.sh:kubeseal -n tools --controller-name=${SEALED_SECRET_CONTOLLER_NAME} --controller-namespace=${SEALED_SECRET_NAMESPACE} -o yaml < delete-ibm-entitlement-key-secret.yaml > ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/apic/environments/single-cluster/config/secrets/ibm-entitlement-key-secret.sh:rm delete-ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/ace/environments/ci/secrets/ibm-entitlement-key-secret.sh: -o yaml > ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/ace/environments/base/secrets/ibm-entitlement-key-secret.sh: -o yaml > ibm-entitlement-key-secret.yaml
As a result, ArgoCD application `apic-config-prod` won't be created properly, instead, showing an error indicating the file `ibm-entitled-registry-credentials-secret.yaml` is not found.
Actually should open this issue in https://github.com/cloud-native-toolkit/multi-tenancy-gitops-apps.
Will open one there. You can close this one if needed.
secret yaml names mismatch -
grep ibm-entitlement-key-secret.yaml * -r
multi-tenancy-gitops-apps/apic/environments/single-cluster/config/secrets/ibm-entitlement-key-secret.sh:kubeseal -n tools --controller-name=${SEALED_SECRET_CONTOLLER_NAME} --controller-namespace=${SEALED_SECRET_NAMESPACE} -o yaml < delete-ibm-entitlement-key-secret.yaml > ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/apic/environments/single-cluster/config/secrets/ibm-entitlement-key-secret.sh:rm delete-ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/ace/environments/ci/secrets/ibm-entitlement-key-secret.sh: -o yaml > ibm-entitlement-key-secret.yaml multi-tenancy-gitops-apps/ace/environments/base/secrets/ibm-entitlement-key-secret.sh: -o yaml > ibm-entitlement-key-secret.yaml