{"id":816,"date":"2020-03-30T12:00:00","date_gmt":"2020-03-30T12:00:00","guid":{"rendered":"http:\/\/bullyrooks.com\/index.php\/2020\/04\/02\/simple-spring-boot-service-to-kubernetes-application-step-12-c6423261a93a\/"},"modified":"2021-02-04T01:58:43","modified_gmt":"2021-02-04T01:58:43","slug":"simple-spring-boot-service-to-kubernetes-application-step-12-c6423261a93a","status":"publish","type":"post","link":"https:\/\/bullyrooks.com\/index.php\/2020\/03\/30\/simple-spring-boot-service-to-kubernetes-application-step-12-c6423261a93a\/","title":{"rendered":"Setting up a Kubernetes Cluster"},"content":{"rendered":"\n
Finally, we\u2019re going to be able to deploy our application. We need to get access to a cluster first.<\/p>\n\n\n\n
Install Tooling<\/h3>\n\n\n\n
We\u2019re going to need more tools in order to get started. Use your OS package management tool to install these tools:<\/p>\n\n\n\n
Kubectl (Interact with a k8s instance)<\/li>
Minikube (Run a cluster locally)<\/li><\/ul>\n\n\n\n
I\u2019m not going to cover how to install these tools, there\u2019s plenty of documentation out there and it would take too much time to cover.<\/p>\n\n\n\n
When you startup minikube it will automatically update your kube config file with the correct settings to talk to minikube.<\/p>\n\n\n\n
Kubectl is the tool that we\u2019ll use to interact with k8s. Specifically, helm will be using it to apply our deployment files that helm generates.<\/p>\n\n\n\n
Setting up Security<\/h3>\n\n\n\n
First we want to setup some secrets to hold configuration that we don\u2019t want to check into git. We could create deployment files in helm and let helm do it for us, but that runs the risk that we accidentally check in a file that has credentials in it. So lets do that by hand for now.<\/p>\n\n\n\n
(line 51)\n {{- range $key, $value := .Values.extraEnv }}\n - name: {{ $key }}\n value: {{ $value | quote }}\n {{- end }}\n{{- if .Values.secretsToEnv }}\n{{ toYaml .Values.secretsToEnv | indent 12 }}\n{{- end }}<\/code><\/pre>\n\n\n\n
Be very careful of editing yaml. Its very sensitive to indentation. Double check my branch to see what the correct yaml file should look like.<\/p><\/blockquote>\n\n\n\n
We also need to update the values.yaml<\/code> to add the mapping for our database credentials. Add this under extraEnv: {}<\/code><\/p>\n\n\n\n
Here we\u2019re reading the secretes file and injecting them into the pod environment. This snake case naming is a spring convention that matches the dot notation in an application properties file. We\u2019re essentially writing spring.datasource.username<\/code> and spring.datasource.password<\/code>. But it a very secure way to do it (as secure as k8s secrets are)<\/p><\/blockquote>\n\n\n\n
The final thing we need to do is point our image configuration at a valid tag. Go into your codefresh docker image registry and pull a tag off of the latest build image<\/p>\n\n\n\n<\/figure>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2021\/02\/13c173K4Aax6bVuzbDyGJug.png?w=960\")
<\/figure>\n\n\n\n