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
{{ message }}
This repository has been archived by the owner on Jan 20, 2021. It is now read-only.
I think an option, or the default, may be to delete and re-add any node(s) that fail to become reach an active-state. Many times this is due to backend kubernetes issues and adding the cleanup logic in the blockchain_platform_manager has a better chance of alleviating the problem then someone on the backend deleting pods.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think an option, or the default, may be to delete and re-add any node(s) that fail to become reach an active-state. Many times this is due to backend kubernetes issues and adding the cleanup logic in the blockchain_platform_manager has a better chance of alleviating the problem then someone on the backend deleting pods.
The text was updated successfully, but these errors were encountered: