If a given cluster is intermittently disappearing from the Gremlin UI despite verified connectivity to the Gremlin API and there are logs in the chao Kubernetes pod indicating a 504 Gateway Timeout, it's possible that a very large update is timing out before successfully completing. This will typically occur in cases where there are very large numbers of namespaces/objects being interacted with.
At present, the workaround is to specify namespaces in the PodSpec (for most installations, this is in the corresponding Helm chart) for the chao pod. For example, this snippet would limit gremlin to looking at the specific namespaces 'default' and 'gremlin':
A full example:
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article