Where do I put my NodePort Spec in my deployment.yaml - kubernetes

Question

I am a total newbe with Helm charts, but I have managed to get a pod with with ApacheDS (LDAP server) running on it. I can exec shell into it and I can login and get responses from the LDAP server.
However, from outside the cluster, I get a connection refused. Looking this up, I "think" I need a NodePort: Kube documentation However, I cannot see where to put that spec. I have tried many things but just cant get it. According to the documentation I need something like this:
spec:
type: NodePort
selector:
app: MyApp
ports:
- port: 10389
targetPort: 10389
nodePort: 30007
Here is my deployment.yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "buildchart.fullname" . }}
labels:
{{- include "buildchart.labels" . | nindent 4 }}
spec:
{{- if not .Values.autoscaling.enabled }}
replicas: {{ .Values.replicaCount }}
{{- end }}
selector:
matchLabels:
{{- include "buildchart.selectorLabels" . | nindent 6 }}
template:
metadata:
{{- with .Values.podAnnotations }}
annotations:
{{- toYaml . | nindent 8 }}
{{- end }}
labels:
{{- include "buildchart.selectorLabels" . | nindent 8 }}
spec:
{{- if .Values.imagePullSecrets }}
imagePullSecrets:
- name: {{ .Values.imagePullSecrets }}
{{- end }}
serviceAccountName: {{ include "buildchart.serviceAccountName" . }}
securityContext:
{{- toYaml .Values.podSecurityContext | nindent 8 }}
containers:
- name: {{ .Chart.Name }}
securityContext:
{{- toYaml .Values.securityContext | nindent 12 }}
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
ports:
- name: admin-port
containerPort: 8080
hostPort: 8080
protocol: TCP
- name: ldap-port
containerPort: 10389
hostPort: 10389
protocol: UDP
livenessProbe:
exec:
command:
- curl ldap://localhost:10389/
initialDelaySeconds: {{ .Values.livenessProbe.initialDelaySeconds }}
periodSeconds: {{ .Values.livenessProbe.periodSeconds }}
readinessProbe:
exec:
command:
- sh
- -c
- curl ldap://localhost:10389/
initialDelaySeconds: {{ .Values.readinessProbe.initialDelaySeconds }}
periodSeconds: {{ .Values.readinessProbe.periodSeconds }}
resources:
{{- toYaml .Values.resources | nindent 12 }}
{{- with .Values.nodeSelector }}
nodeSelector:
{{- toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.affinity }}
affinity:
{{- toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.tolerations }}
tolerations:
{{- toYaml . | nindent 8 }}
{{- end }}
How do I open this port to the rest of the world? Or at least the box the container is on.

Answer 1

Yes, you need to create a Service for your deployment.
Also, I suggest you do it without hardcoding, because easier to change a value in the values.yaml file than edit templates files for adding a new hardcode values.
In the deployment.yaml set:
...
{{ if .Values.ports }}
ports:
{{ range .Values.ports }}
- name: {{ .name }}
containerPort: {{ .containerPort }}
protocol: {{ .protocol }}
{{ end }}
{{ end }}
...
In the values.yaml set:
ports:
- name: admin-port
containerPort: 8080
nodePort: 8080
protocol: TCP
- name: ldap-port
containerPort: 10389
nodePort: 10389
protocol: UDP
Create service.yaml file and set
apiVersion: v1
kind: Service
metadata:
name: {{ include "buildchart.fullname" . }}
labels:
{{- include "buildchart.labels" . | nindent 4 }}
spec:
type: {{ .Values.service.type }}
ports:
{{ range .Values.ports }}
- port: {{ .nodePort }}
targetPort: {{ .containerPort }}
protocol: {{ .protocol }}
name: {{ .name }}
{{ end }}
selector:
{{- include "buildchart.selectorLabels" . | nindent 4 }}

Answer 2

You should be adding that as a Service object spec not in your deployment object.
For example,
apiVersion: v1
kind: Service
metadata:
name: my-app-service
spec:
type: NodePort
selector:
app: MyApp
ports:
- port: 10389
targetPort: 10389
nodePort: 30007