DEV commit code to SCM > Pull Request > Webhook in Jenkins > Unit tests, Sonarqube integration > Build Docker Image \ tag it \ push to AWS ECR > Integration tests > Deploy tagged image from AWS ECR to our AWS EKS cluster > Notify of status
Secrets are stored in Ansible playbook in SCM.
YAML files are obviously stored in SCM, which is stored in each repo in a directory called .\kubernetes
Hi,
We deploy using the following process:
DEV commit code to SCM > Pull Request > Webhook in Jenkins > Unit tests, Sonarqube integration > Build Docker Image \ tag it \ push to AWS ECR > Integration tests > Deploy tagged image from AWS ECR to our AWS EKS cluster > Notify of status
Secrets are stored in Ansible playbook in SCM.
YAML files are obviously stored in SCM, which is stored in each repo in a directory called .\kubernetes
Do you use Jenkins or Jenkins X?
I didn't use Jenkins recently. Can you give any tips for using Jenkins in a Kubernetes environment?
Hi,
Jenkins (not X) is used. Something similar to this with environmental variables defined for k8sClusterCredentialName and k8sMasterUrl
"...Secrets are stored in Ansible playbook in SCM..." We talking API keys / web tokens?
Yes, oAuth & DB connection strings
Secrets are stored in Ansible playbook in SCM. What does this really mean?
Misworded, secrets are stored in a yaml file, which is encrypted. ansible-vault is used to encrypt/decrypt. The playbook references the secrets.
Yes, ansible-vault