Bartra, Rick 35f14aa728 Create secrets from project's jarvis.yaml
Each CNF project now has a jarvis.yaml defining credentials for
harbor and docker, kubeconfig, and certs. The existing ldap
users are used in the jarvis.yaml for both the staging and
non-staging phases of the CI.

The kubeconfig and harbor-ca entries of the jarvis.yaml are
populated during the 800 script and adds those entries as
base64 encoded data so that the required format (indentations and
spacing) is maintained. The Task-createProjectAccess then decodes
the kubeconfig and harbor-ca and creates the secrets for them in
the correct namespace. Secret creation all takes place in the
Task-createProjectAccess.

Change-Id: If0c243416323e36a6f7797d8d378961552193c0d
2021-03-11 12:03:41 -05:00

122 lines
2.4 KiB
YAML

dev:
jarvis-aio:
# Left blank as the kubeconfig is added in during execution of the 800-deploy-jarvis-projects.sh script
# The kubeconfig is added in from ~/.kube/config
kubeconfig:
# Left blank as the harbor-ca is added in during execution of the 800-deploy-jarvis-projects.sh script
# The harbor-ca is added in from /etc/jarvis/certs/ca/ca.pem
harbor-ca:
helm:
username: ausf-harbor
password: harbor-user-password
helm-staging:
username: ausf-harbor-staging
password: harbor-staging-user-password
harbor:
username: ausf-harbor
password: harbor-user-password
email: example@gmail.com
server: harbor-core.jarvis.local
harbor-staging:
username: ausf-harbor-staging
password: harbor-staging-user-password
email: example@gmail.com
server: harbor-core.jarvis.local
# clusterA:
# kubeconfig:
# harbor-ca:
# helm:
# username:
# password:
# helm-staging:
# username:
# password:
# harbor:
# username:
# password:
# email:
# server:
# harbor-staging:
# username:
# password:
# email:
# server:
# sil:
# clusterA:
# kubeconfig:
# harbor-ca:
# helm:
# username:
# password:
# helm-staging:
# username:
# password:
# harbor:
# username:
# password:
# email:
# server:
# harbor-staging:
# username:
# password:
# email:
# server:
# clusterB:
# kubeconfig:
# harbor-ca:
# helm:
# username:
# password:
# helm-staging:
# username:
# password:
# harbor:
# username:
# password:
# email:
# server:
# harbor-staging:
# username:
# password:
# email:
# server:
# prod:
# clusterA:
# kubeconfig:
# harbor-ca:
# helm:
# username:
# password:
# helm-staging:
# username:
# password:
# harbor:
# username:
# password:
# email:
# server:
# harbor-staging:
# username:
# password:
# email:
# server:
# clusterB:
# kubeconfig:
# harbor-ca:
# helm:
# username:
# password:
# helm-staging:
# username:
# password:
# harbor:
# username:
# password:
# email:
# server:
# harbor-staging:
# username:
# password:
# email:
# server: