GitHub user heisenbergs-uncertainty edited a comment on the discussion: reverse
proxy for ui - nginx
Just saw that it's k8s.
Follow my process that I outlined above.
The current helm chart does not always successfully restart the backend service
due to multiple poss accessing the same Persistent Volume Claim. When this
happens, the extensions service will complete its restart before the backend
and register with the old service and will prevent the two services from
correctly coordinating.
Here are the steps I take when I redeploy if I have issues with the extensions
service:
- [ ] Redeploy with new updates
- [ ] `kubectl get rs -n ${streampipes_namespace}`
- [ ] Delete the old record set. It will be whichever one is older.
- [ ] Delete the new backend pod to remove the volume error
- [ ] Restart the extensions service
If this works then you can repeat this in the future.
I am currently working on a new helm chart and seeing if I can resolve this
issue. I started it a long time ago but haven't had the time since I had a baby
shortly after opening the PR.
Hopefully I can get back to it soon as the helm chart is very outdated in its
current state.
You should also note that I don't use the official chart but use my own chart.
GitHub link:
https://github.com/apache/streampipes/discussions/3612#discussioncomment-13227858
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
