Cluster Automotion with Stackbooster Guide #
Introduction #
This Guide refers to the process of transitioning your Kubernetes clusters to StackBooster’s automated management platform. Depending on how your cluster was initially created or connected, different movement workflows are available to ensure a smooth onboarding experience that matches your cluster’s current configuration and access level.
Understanding Your Options #
When you navigate to your Cluster page, StackBooster automatically displays the appropriate cluster movement workflow in the top bar based on:
- How the cluster was initially created (newly provisioned vs. pre-existing)
- Current access permissions (read-only vs. read-write)
- Whether automation agents have been deployed
This guide explains the four available cluster movement workflows and helps you understand which one applies to your specific situation.
Available Cluster Automation Workflows #
StackBooster provides four distinct cluster automation workflows, each designed for specific cluster configurations and onboarding scenarios.
Option 1: Read-Only Cluster Migration #
Available When: You have an existing cluster that was initially onboarded with read-only access and want to upgrade to full automation capabilities. More Detailes
Purpose #
This workflow enables you to upgrade clusters that were originally connected in read-only monitoring mode to full automation with read-write access. It’s ideal when you started with basic observability and are now ready to enable active management features.
Workflow Steps (6 Total) #
Step 1: Connect Cluster
- Passed
Step 2: Connect Cloud Account
- Link your cloud provider account (AWS, Azure, or GCP)
- Provide credentials with appropriate permissions
- Enable StackBooster to interact with cloud resources
- Can Choose between Autoscalling or Full Control. More Detailes
Step 3: Enable Full Agent Mode
- Upgrade from read-only observer to read-write agent
- Deploy the full automation agent to your cluster More Detailes
Step 4: Migration Template
- Review and configure migration parameters
- Define resource allocation strategies
- Customize automation settings based on your requirements More Detailes
Step 5: Roll Cluster
- Execute the migration process across all nodes
- Apply new configurations and agent deployments
- Monitor rollout progress in real-time More Detailes
Step 6: Configure Automation
- Finalize automation policies and scaling rules
- Set up optimization parameters
- Activate automated workload management More Detailes
Expected Outcome #
After completing this workflow, your cluster transitions from passive monitoring to active automation. StackBooster gains read-write access and can manage workloads, perform auto-scaling operations, and implement cost optimizations automatically.
Option 2: Discover Cluster (Read-Write) #
Available When: Onboarding an existing Kubernetes cluster where you can provide read-write access from the start. More Detailes
Purpose #
This workflow streamlines onboarding for existing clusters when you have full permissions and want to enable automation capabilities immediately without starting in read-only mode.
Workflow Steps (6 Total) #
Step 1: Connect Account
- Passed with providung Autoscalling or Full Controle.
Step 2: Connect Cluster
- Passed.
Step 3: Enable Full Agent Mode
- Agent Installed.
Step 4: Migration Template
- Review and configure migration parameters
- Define resource allocation strategies
- Customize automation settings based on your requirements More Detailes
Step 5: Roll Cluster
- Execute the migration process across all nodes
- Apply new configurations and agent deployments
- Monitor rollout progress in real-time More Detailes
Step 6: Configure Automation
- Finalize automation policies and scaling rules
- Set up optimization parameters
- Activate automated workload management More Detailes
Expected Outcome #
Your existing cluster is fully onboarded with complete automation capabilities enabled. StackBooster has immediate read-write access and can manage workloads, scale resources, and optimize cluster performance from the start.
Option 3: Discover Cluster (Read-Only) #
Available When: Onboarding an existing Kubernetes cluster starting with read-only access for safety or compliance requirements.
Purpose #
This comprehensive workflow is designed for cautious onboarding scenarios where you want to start with limited read-only access, validate the integration, and then gradually upgrade to full automation. It provides maximum control and visibility at each permission level.
Workflow Steps (7 Total) #
Step 1: Connect Account
- Passed in Read-only mode.
Step 2: Connect Cluster
- Passed.
Step 3: Update Cloud Account
- Upgrade cloud account permissions as needed
- Ensure sufficient access for future automation steps
- Verify enhanced credential configuration
Step 4: Enable Full Agent Mode
- Transition from read-only observer to read-write agent
- Deploy the full automation agent
- Grant necessary permissions for active cluster management
Step 5: Migration Template
- Review and configure migration parameters
- Define resource allocation strategies
- Customize automation settings based on your requirements More Detailes
Step 6: Roll Cluster
- Execute the migration process across all nodes
- Apply new configurations and agent deployments
- Monitor rollout progress in real-time More Detailes
Step 7: Configure Automation
- Finalize automation policies and scaling rules
- Set up optimization parameters
- Activate automated workload management More Detailes
Expected Outcome #
Your cluster successfully transitions from initial read-only observation through permission upgrades to full automation capabilities. This gradual approach ensures validation at each step, resulting in a fully automated cluster with comprehensive management features.
Option 4: Create New Cluster #
Available When: Creating a brand new Kubernetes cluster through the StackBooster platform. More Detailes
Purpose #
This streamlined workflow is for provisioning entirely new clusters managed by StackBooster from inception. Since the cluster is created by the platform, it automatically includes the necessary integrations and permissions, requiring fewer setup steps.
Workflow Steps (4 Total) #
Step 1: Connect Account
- Passed in Full Control.
Step 2: Create Cluster
- Passed
Step 3: Connect Cluster
- Establish connection to the newly created cluster
- Verify cluster health and accessibility
Step 4: Configure Automation
- Finalize automation policies and scaling rules
- Set up optimization parameters
- Activate automated workload management More Detailes
Expected Outcome #
A fully functional, StackBooster-managed Kubernetes cluster is created in your cloud environment with automation capabilities enabled from the start. The cluster is optimally configured for the platform’s management features without requiring migration or permission upgrades.
Workflow Comparison #
Use this table to quickly understand the differences between the four cluster movement options:
| Feature | Read-Only Migration | Discover (Read-Write) | Discover (Read-Only) | Create New Cluster |
|---|---|---|---|---|
| Total Steps | 6 | 6 | 7 | 4 |
| Starting Point | Existing read-only cluster | Existing cluster | Existing cluster | No existing cluster |
| Initial Access Level | Read-only | Read-write | Read-only | Full (platform-created) |
| Cloud Account Connection | Step 2 | Step 1 | Step 1 | Step 1 |
| Permission Upgrade Required | Yes (Step 3) | No (starts with full access) | Yes (Steps 3-4) | No (inherent) |
| Cluster Creation | No | No | No | Yes (Step 2) |
| Best For | Upgrading monitored clusters | Quick onboarding with existing permissions | Cautious, gradual onboarding | New deployments |
| Use Case | You’ve been observing and want to enable automation | You have full permissions and want immediate management | You want to validate before granting full access | Starting fresh with optimized configuration |
Frequently Asked Questions #
How do I know which workflow applies to my cluster? #
StackBooster automatically detects your cluster’s configuration and displays the appropriate workflow in the top bar of the Cluster page. You don’t need to manually select which workflow to use.
Can I switch between workflows? #
No, the workflow is determined by your cluster’s current state and creation history. However, completing a workflow changes your cluster’s capabilities (for example, completing a read-only workflow upgrades your cluster to full automation).
What happens if a step fails during cluster movement? #
The workflow pauses at the failed step. You can review error messages in the Events log, correct any issues, and retry the step. Progress on completed steps is saved automatically.
How long does each workflow take? #
Timing varies based on cluster size and complexity:
- Read-Only Migration: 25-35 minutes
- Discover Cluster (Read-Write): 25-35 minutes
- Discover Cluster (Read-Only): 25-35 minutes
- Create New Cluster: 20-25 minutes (excluding cloud provider provisioning time)
Can I pause a workflow and resume later? #
Yes, all workflows save progress automatically. You can safely navigate away from the page and return later to continue from where you left off.
What permissions are required for each workflow? #
Specific permissions depend on your cloud provider and the workflow type. Generally, you’ll need:
- Kubernetes: Cluster admin access or equivalent RBAC permissions
- Cloud Provider: Permissions to read/modify resources (varies by workflow)
Detailed permission requirements are displayed during each relevant step. For comprehensive information, see the Cloud Permissions Guide.
What if I want to change my cluster’s access level later? #
If you initially onboarded a cluster with read-only access and later want full automation, use the Read-Only Cluster Migration workflow to upgrade your access level and enable full agent mode.
Next Steps #
After completing your cluster movement workflow:
- Deploy Applications: Start deploying workloads to your newly managed cluster
- Monitor Performance: Use StackBooster’s dashboards to track cluster health and resource utilization
- Configure Node Templates: Set up custom node templates for optimal scaling
- Review Activities: Check the Cluster Activities log for a complete audit trail
- Optimize Costs: Leverage AI-powered recommendations for cost reduction
Getting Help #
If you encounter issues during any cluster movement workflow:
- Check Status Messages: Review error details displayed at each step
- Verify Permissions: Ensure your cloud credentials have the required permissions
- Review Prerequisites: Confirm your cluster meets minimum requirements
- Check Events Log: Review the detailed events log for troubleshooting information
- Access Documentation: Visit our Documentation for comprehensive guides
- Contact Support: Use the Need Help? feature or reach out to our support team through the platform