Selector matchlabels name include remind me webname

selector:
matchLabels:
name: {{ include "remind-me-web.name" . }}
template:

110
metadata:
labels:
name: {{ include "remind-me-web.name" . }}
spec:
containers:
- name: {{ .Chart.Name }} # the substitution value of this
parameter is present in Chart.yaml file.
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
ports:
- name: http
containerPort: 80
protocol: TCP
---
To keep the chart configurable by the end user, we have used several parameters in our
definitions. Let’s define the default values of these parameters in the Values.yaml file. Modify
the code in the file to reflect the following code listing.
Code Listing 97: Define default values
replicaCount: 2
nameOverride: ""
fullnameOverride: ""
service:
port: 80
targetPort: 80
nodePort: 31120
image:
repository: "kubernetessuccinctly/remind-me-web"
tag: "1.0.0"
As a good practice, let’s now modify the code in the Chart.yaml file to add metadata for our
chart to help the users. Modify the code to reflect the following code listing.
Code Listing 98: Metadata
apiVersion: v1
appVersion: "1.0"
description: Helm chart for remind-me-web v1
name: remind-me-web
version: 0.1.0
Our chart is now ready for deployment to our cluster. In the next section, we will deploy our
chart to our cluster and perform some common operations on it.

111
Deploying charts
Now that our chart is ready, let’s validate whether our chart is appropriately formed by
processing it through a linter. Execute the following command in your terminal to validate your
chart.
Code Listing 99: Validate chart
helm lint ./remind-me-web
Figure 63: Output validate chart
Now that we have a green signal from the linter, let’s move on to deploy this chart on the local
cluster with this command.
Code Listing 100: Deploy chart
helm install --name remind-me-web ./remind-me-web
In this command, you can see that we have provided the value of the .Release.Name
parameter in the command. We have used this parameter in the /templates/_help.tpl template
and the NOTES.txt file.
Figure 64: Installing chart

112
Your service should not be available on . Congratulations! You have
successfully deployed your first chart on a live cluster.
You can modify values in your Deployment template or the Values template and reinstall the
chart to make any modifications to your deployment.
Debugging charts
Writing charts can be tricky because the templates are rendered on Tiller, which in turn sends
the generated templates to the Kubernetes API server for processing. If you want to check the
generated value of an expression, then comment out the expression that you want to test and
execute the following command.
Code Listing 101: Check chart expression
helm install ./remind-me-web --dry-run --debug
This command will return the manifest with the comment intact. For example, if we want to
evaluate the value of the following complex expression in the helper’s template, we can copy
the relevant section, paste it in either the deployment or service template, and execute the
previous command.