I have a question about restarting Sametime on Kubernetes services after a reboot for Mongo-DB server or LDAP server.
In ST 11.6 we restart
- the catalog pod after Mongo-DB server restart (no meeting rooms available)
> kubectl scale deployment catalog --replicas=0
> kubectl scale deployment catalog --replicas=1
- the auth pod after LDAP server restart (no meeting login possible)
> kubectl scale deployment catalog --replicas=0
> kubectl scale deployment catalog --replicas=1
- the web pod after community server restart (chat within meeting seems loading)
> kubectl scale deployment catalog --replicas=0
> kubectl scale deployment catalog --replicas=1
Are there any suggestions with ST 12 ?
I know i can unload the complete deployment by helm uninstall sametime but sometimes it is faster only to restart the corresponding pod(s).