Restore the defaults for targetPort when not explicitly set (#26)

The original intent with having separate `httpPorts` and `httpsPorts` was to be able to specify multiple ports of each kind, mapped to the `http` and `https` ports, respectively, on the haproxy-ingress pod. When the ability to set the `targetPort` was added by 00ce053, backwards compatibility was broken by removing the defaults.

Fixes #25

haproxy-ingress/templates/controller-service.yaml

@@ -52,7 +52,7 @@ spec:
     - name: "http-{{ .port }}"
       port: {{ .port }}
       protocol: TCP
-      targetPort: {{ .targetPort }}
+      targetPort: {{ .targetPort | default "http" }}
     {{- if (not (empty .nodePort)) }}
       nodePort: {{ .nodePort }}
     {{- end }}
@@ -61,7 +61,7 @@ spec:
     - name: "https-{{ .port }}"
       port: {{ .port }}
       protocol: TCP
-      targetPort: {{ .targetPort }}
+      targetPort: {{ .targetPort | default "https" }}
     {{- if (not (empty .nodePort)) }}
       nodePort: {{ .nodePort }}
     {{- end }}