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
Folks, I observed an issue with init jobs config (for deployments relay on mongodb), specifically when mongoDB set to run in standalone architecture.
k8s do not create headless service for standalone mode, hence a service/endpoint should be referred in place of headless services.
Following need some logical handing for standalone mode. until nc -z -w 2 {{ $.Release.Name }}-mongodb-headless {{ $mongodb_port }} && echo mongodb ok;
Folks, I observed an issue with init jobs config (for deployments relay on mongodb), specifically when mongoDB set to run in standalone architecture.
k8s do not create headless service for standalone mode, hence a service/endpoint should be referred in place of headless services.
Following need some logical handing for standalone mode.
until nc -z -w 2 {{ $.Release.Name }}-mongodb-headless {{ $mongodb_port }} && echo mongodb ok;
--->
until nc -z -w 2 {{ $.Release.Name }}-mongodb {{ $mongodb_port }} && echo mongodb ok;
`
let me know if anyone able to reproduce it.
Thanks
The text was updated successfully, but these errors were encountered: