Closed jackrh closed 6 months ago
I don't think websocket service ever need to have ingress object at all. Instead of adding template for it, removing ingress part from values.yaml would be better. @talboren @shahargl what do you guys think?
I don't think websocket service ever need to have ingress object at all. Instead of adding template for it, removing ingress part from values.yaml would be better. @talboren @shahargl what do you guys think?
Hmm, but we do need ingress for the websocket service if we want FE clients to be able to get push notifications about newly added alerts (real-time updates) -- lmk if I miss understood something
I don't think websocket service ever need to have ingress object at all. Instead of adding template for it, removing ingress part from values.yaml would be better. @talboren @shahargl what do you guys think?
Hmm, but we do need ingress for the websocket service if we want FE clients to be able to get push notifications about newly added alerts (real-time updates) -- lmk if I miss understood something
Actually you don't need ingress for that if you are not going to access your websocket service from another cluster. If both websocket and fe services are in same cluster it is kind of best practice to communicate them over services. like: keep-websocket.<namespace>.svc.cluster.local:6001
Contributor
gotcha! thanks for the detailed explanation! @pehlicd do you want to craft a PR to issue that?
yeah sure
Description of the bug
If you add an ingress to websocket in your values.yaml it will never render the necessary yaml because the websocket template file is missing.
Steps To Reproduce
Additional Information
No response