Connect Existing Cluster
Bring Your Own Cluster (BYOC)
The BYOC feature lets you seamlessly connect and manage your pre-existing Kubernetes clusters within the Scoutflo Deploy platform. This is ideal for users who already have clusters set up and wish to use Scoutflo’s advanced management, monitoring, and application deployment capabilities without needing to create a new one. Here's how you can connect your existing cluster:
Step 1: Accessing the Cluster Connection Interface
Navigate to "My Cluster":
After successfully connecting your Git account, proceed to manage your Kubernetes clusters.
On the left sidebar, find the 'My Cluster' section located below the workspace dropdown. This is your central hub for all cluster management tasks.
Add a New Cluster:
Click on the "+Add Cluster" button at the top right corner of the 'My Cluster' screen.
Choose the "Connect a Cluster" option to open a new screen dedicated to connecting your existing Kubernetes cluster.
Step 2: Filling in the Required Details
When connecting your existing cluster, you’ll need to provide some details. Here’s a breakdown of each input field and its significance:
Credentials Name (Required):
Provide a descriptive name to identify the AWS credentials you’ll be using for this cluster. This name helps you organize and differentiate between various credential sets, especially when managing multiple clusters with different accounts.
Examples: "Production AWS Credentials," "Development Team AWS Account," or "John’s Personal AWS."
AWS Access Key (Required):
Enter your AWS Access Key ID, which is needed to authenticate and connect to your existing EKS cluster. This key must have permissions for EKS management and access to relevant resources.
Note: Ensure you have the right IAM permissions configured to allow Scoutflo Deploy to manage your cluster.
AWS Secret Key (Required):
Provide the Secret Access Key associated with your AWS Access Key ID. This key is used to securely authenticate your AWS account.
Important: Keep this key confidential and avoid sharing it or storing it in insecure locations, as it provides access to your AWS resources.
AWS Region (Required):
Specify the AWS region where your existing EKS cluster is hosted. AWS regions are geographic locations where AWS data centres are located, and selecting the correct region ensures that Scoutflo Deploy can locate and access your cluster.
Examples: "us-east-1" (North Virginia), "eu-central-1" (Frankfurt), etc.
Cluster Name (Required):
Provide the exact name of your existing EKS cluster. This is the unique identifier that Scoutflo Deploy will use to connect and manage your cluster.
Make sure to input the name as it appears in your AWS console for accurate identification.
By following these steps, Scoutflo Deploy will establish a connection with your existing Kubernetes cluster, enabling you to manage, monitor, and deploy applications as if they were created directly within the platform. The BYOC feature ensures that you can leverage Scoutflo’s capabilities without the need to reinvest in setting up new infrastructure, making it a flexible and powerful tool for managing Kubernetes clusters across various environments.
Monitoring:
Grafana
Prometheus
Alert Manager
Security:
HCP Vault
Tools:
Argo CD
Atlantis
AWS Apps:
CoreDNS
Kube-Proxy
Amazon EBS CSI Driver
Amazon VPC CNI
We add the above products out of the box to enable cluster observability features.
Critical Tradeoffs: Adding an Existing Cluster vs. Creating a Cluster in Scoutflo Deploy
Scoutflo Deploy offers two flexible options for integrating clusters into your deployment workflow: adding an existing Amazon EKS cluster or creating a new cluster directly within the platform. Each approach has its unique benefits, and understanding these will help you choose the best option for your needs.
Adding an Existing EKS Cluster
Quick Integration: If you already have a configured EKS cluster, connecting it to Scoutflo Deploy is faster than setting up a new one. This lets you leverage your current infrastructure for immediate deployments, minimizing setup time.
Leverage Existing Resources: By integrating your existing EKS cluster, you utilize pre-configured compute instances, networking, and security settings, ensuring consistent resource management without needing to provision new ones.
Cost-Efficient: Since you’re using an already existing cluster, there's no additional cost for creating new infrastructure. This can be beneficial for organizations with established cloud environments.
Creating a New EKS Cluster with Scoutflo Deploy
Optimal Configuration and Best Practices: Scoutflo Deploy offers a guided setup for creating a new EKS cluster, ensuring that your cluster is configured with best practices in mind. This includes security, networking, and performance optimizations tailored for seamless integration with Scoutflo Deploy.
Guaranteed Compatibility: Since the cluster is created within Scoutflo Deploy, you eliminate compatibility concerns. The cluster will be fully optimized for Scoutflo’s features, guaranteeing a smooth and efficient deployment process.
Simplified Lifecycle Management: With Scoutflo Deploy handling the entire cluster lifecycle—from creation to upgrades—you enjoy a hassle-free management experience. This lets you focus on application deployments without worrying about infrastructure maintenance.
Cost and Performance Optimization: When creating a new cluster, Scoutflo Deploy ensures optimal resource allocation, which can lead to both improved application performance and cost efficiency. This helps you strike the right balance between performance and expenses.
Enhanced Visibility and Troubleshooting: A cluster created within Scoutflo Deploy provides complete visibility and control, making it easier to troubleshoot, monitor, and resolve issues. You have direct access to detailed insights and metrics, simplifying management.
Choosing the Right Approach
The ideal choice depends on your specific situation and priorities. Consider the following factors:
Existing EKS Cluster Availability: If you already have an EKS cluster with sufficient capacity, adding it might be the quickest route.
Control and Visibility: Are you looking for complete visibility and seamless integration with Scoutflo Deploy features? If so, creating a new cluster might be more suitable.
Management Complexity: Do you prefer a managed experience where Scoutflo Deploy handles lifecycle management, upgrades, and optimizations? If yes, creating a new cluster within Scoutflo Deploy is the way to go.
Our Recommendation
For most users, creating a new cluster within Scoutflo Deploy is the recommended option. This ensures you gain the benefits of optimal configuration, guaranteed compatibility, simplified management, and enhanced cost efficiency. However, if you already have a well-managed EKS cluster with sufficient resources and need to get started quickly, adding your existing cluster can be a practical and efficient choice.
Last updated
