v1.0.11 - Fix Cluster Auto-Start Issue
What's Changed
π Bug Fixes
- Fixed cluster auto-start: Added explicit cluster start step to ensure cluster is running before app deployment
- Improved cluster readiness check: Enhanced wait logic with cluster status verification
π Technical Details
- Added step
- Increased wait time to 90 seconds for better cluster initialization
- Added cluster status check with command
- Renamed job from to for clarity
π‘ Why This Fixes the Issue
The previous workflow only deployed cluster configuration but didn't ensure the cluster was actually running. If the cluster was stopped, the app deployment would fail. Now the workflow explicitly starts the cluster and waits for it to be ready before deploying the app.
This release should resolve the issue where deployments don't start stopped clusters.