search

meilisearch / meilisearch-kubernetes

Meilisearch on Kubernetes Helm charts and manifests
https://www.meilisearch.com
MIT License
212 stars 59 forks source link

service:NodePort does not match the correct NodePort #47

Closed simeonexo closed 3 years ago

simeonexo commented 3 years ago

I defined the #NodePort to be exposed, for example, 31009, in values.yaml. But when I installed the helm chart, the real NodePort ranged from 31000 to 33000 and was never the specified 31009.

eskombro commented 3 years ago

Hi @simonxxz

Can you show us an example of your configuration?

simeonexo commented 3 years ago

Hi @simonxxz

Can you show us an example of your configuration?

Here is my config: service: type: NodePort port: 7700 NodePort: 31009

Is there anything config I have to add to make nodeport work correctly?

To add, I also tried lowercase nodePort and putting port below nodePort, and neither worked.

eskombro commented 3 years ago

HI @simonxxz

Indeed, the chart is not prepared to add the nodePort field, so the port you are specifying is basically ignored. I detailed this on this issue: https://github.com/meilisearch/meilisearch-kubernetes/issues/50

Feel free to add any useful info in there, and if you feel like doing a fix on it it would be amazing to have your contribution! :)

(Closing in favor of #50, feel free to re-open if needed)