You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In values.yaml it is possible to define the Service type. But if a user defines it as a NodePort service, there is no field in the chart to specify the nodePort, so kubernetes will allocate a random port.
In a NodePort Service, the nodePort field is defined as follows:
But MeiliSearch chart is not prepared to let the user specify this nodePort Value in values.yaml and integrate it in the template (cf. see here).
The service template could check if the Service type is NodePort, and in that case, add the nodePort field to the Service Template.
The text was updated successfully, but these errors were encountered:
87: Support for specifying Nodeport in service r=alallema a=Thearas
# Pull Request
## What does this PR do?
Implement #50.
Co-authored-by: Thearas <[email protected]>
In
values.yaml
it is possible to define the Service type. But if a user defines it as aNodePort
service, there is no field in the chart to specify thenodePort
, so kubernetes will allocate a random port.In a NodePort Service, the
nodePort
field is defined as follows:But MeiliSearch chart is not prepared to let the user specify this
nodePort
Value invalues.yaml
and integrate it in the template (cf. see here).The service template could check if the Service type is
NodePort
, and in that case, add thenodePort
field to the Service Template.The text was updated successfully, but these errors were encountered: