Quality of Life for provider/Customers using deployments on akash console. #827
Description
First, I want to acknowledge the great job that OCL has done with the providers and improving the Akash network. The progress so far has been very good.
This issue is aimed at further enhancing the usability of providers and the Akash Console, particularly during network upgrades.
Problem:
When upgrading the network, providers may experience downtime, boot loops, or lose sync, causing users to temporarily lose access to their deployments. This can lead to disruptions, uncertainty, and potential issues during the upgrade process.
Proposed Solution:
Implement a static backup mechanism that allows the Akash Console to continue functioning with current leases while the blockchain/network is being upgraded in the background.
Ensure that users can still access the console and their deployments, preventing work from being stalled for hours due to unforeseen upgrade issues.
Introduce a provider.yaml setting to disable automatic provider restarts when it loses sync, reducing unnecessary downtime.
This could greatly improve the overall experience for both providers and users, ensuring more seamless network upgrades with minimal service interruptions.
Would love to hear thoughts from the community on this.