Allow defining Service type

[mattermost]

Allow defining Service type

[nicolas-goudry]

@Szymongib Thanks for your quick reply.

Regarding the workaround, your proposal is valid, but as of v1.14.0 I would still need to create another Ingress object than the one created by mattermost-operator, leaving me with:

• a Service object of type ClusterIP, created by operator, which will never be used
• an Ingress object, created by operator and forever stuck in Scheduled for sync state
• another Service object of type NodePort, created manually
• another Ingress object, created manually and bound to the manually created Service

It will be even better when the next version is released (with better Ingress management), then I would only need to disable the Ingress creation by mattermost-operator and create a NodePort Service object as well as a custom Ingress object, leaving me only with a ClusterIP Service which will never be used.

This is fine for now, but I’m looking forward to have this feature implemented 🙂

[Szymongib]

Thanks for the detailed explenation @nicolas-goudry. I will look into this.

As for the workaround, you should be able to just create another service pointing at Mattermost pods and customize it to your own demands.

[gabrieljackson]

We are opening this feature request as a help wanted ticket for anyone interested in implementing it.