Feature: create `service.targetPort` parameter or default to `nextcloud.containerPort` for targetPort in service template

[jessebot]

Description of the change

I feel like we should allow users to set a service.targetPort :

helm/charts/nextcloud/values.yaml

Lines 366 to 370 in eedad34

	service:
	type: ClusterIP
	port: 8080
	loadBalancerIP: nil
	nodePort: nil

It might also make sense to default to nextcloud.containerPort here if service.targetPort is not set or not chosen for implementation:

helm/charts/nextcloud/templates/service.yaml

Line 18 in eedad34

targetPort: http

Benefits

This allows users to use different container ports, such as 9000, to have a more direct connection to the ingess-nginx controller directly, instead of using the nginx container.

Possible drawbacks

Not sure if we should also set port name fields? We use http a lot and this could get confusing?

Additional information

Happy to submit a PR for this. It would also be part of the work to implement #367 down the line.

[jessebot]

Added #386 as a draft PR, because I think this is a good idea, but in the PR, I just decided to default to nextcloud.containerPort for the service targetPort to reduce complexity. Open to better ways to do this.

[jessebot]

relates to the following PRs, so I'll close my draft if these get merged first:

• Fix(nginx-config): Listen port based on nextcloud.containerPort #278
• Allow probe checks and Service to use containerPort if specified #316

[provokateurin]

@jessebot would you mind closing or updating the other PRs?