Skip to content

[bug] secret yaml names mismatch #223

Description

@mkz100

secret yaml names mismatch -

  1. Gitops expects ibm-entitled-registry-credentials-secret.yaml
multi-tenancy-gitops-apps/apic/environments/single-cluster/config/kustomization.yaml:

- secrets/ibm-entitled-registry-credentials-secret.yaml
  1. 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions