Scoutflo Documentation
  • 🚀Welcome to Scoutflođź’™
  • Overview
    • What is Scoutflo?
    • Getting Started
    • Scoutflo Architecture
    • Basic Concepts
    • Our Products
  • Our Products
    • Scoutflo Deploy
    • Scoutflo Atlas
      • About
      • Key Features
      • Scoutflo Sandbox
        • How to use
        • Available Product Sandboxes
      • Scoutflo Health Score
        • Overview
        • Key Metrics
          • Security Key Elements
          • Code Quality & Maintenance Key Elements
          • Support Key Elements
          • Community Activeness Key Elements
          • Business Readiness Key Elements
        • Calculation
        • Use case of these Scores
        • Process of Score calculation
        • FAQ
      • Product Qualification
      • Find the right product
      • Product Information and Maintenance
      • Product Stakeholders
  • Key Feature
    • Infrastructure Provisioning
      • Create a new Cluster
        • Add Credentials
        • VPC Configuration
      • Edit an existing Cluster
        • Security Scans for Cluster
      • Delete a Cluster
    • Service Deployment
      • Service Onboarding
      • Service Cost Prediction
      • Service Deployment
      • Delete a Service
    • Helm Service Deployment
      • Customized Helm Deployment
      • Open Source Helm Deployment
      • Open Source Service Catalog
      • Edit an App
      • Delete an App
    • Database Deployment
    • RBAC
      • Set Up your custom Roles
    • Workspace
    • Dora Dashboard
    • Kubernetes Dashboard
    • Notification (Coming Soon)
    • Alert Management
      • Default Alert Rules
  • Guide
    • Terraform and Scoutflo
    • AWS EKS Best Practices Guide
    • Kubernetes and Scoutflo
    • ArgoCD and Scoutflo
    • Connect your Cloud
    • Scoutflo Deploy Free Trial Cluster
    • Add-on deployments
    • Custom Configurations
    • Terminology Guide
    • Workflow Action ID
  • Integrations
    • Scoutflo Integration
    • Version Control tool
      • GitHub App
    • Container Registry
      • AWS ECR Container Registry
      • Docker Hub Container Registry
    • Slack
    • Scoutflo Add-Ons
  • Fundamentals
    • GitOps with Scoutflo
    • Container/OCI Registry
    • Monitoring
    • AWS EKS Cluster
    • List of IAM permissions for your scoutflo IAM user on AWS
  • FAQs
    • General
    • Scoutflo Atlas
    • Scoutflo Deploy
    • Scoutflo Sandbox
    • Contact Us
  • Glossary
Powered by GitBook
On this page
  1. FAQs

Scoutflo Deploy

PreviousScoutflo AtlasNextScoutflo Sandbox

Last updated 1 year ago

How does Scoutflo Deploy work?

Check out our product documentation -

What does Scoutflo Deploy automate?
  • Cluster addition. [your existing cluster]

  • Cluster creation on your preferred cloud infrastructure. [alpha]

  • Self-hosting the open-source product on the selected cluster.

What cloud infrastructures are you catering to right now?

We are currently catering to AWS Cloud infrastructure. The aim is to expand our coverage across GCP & Azure Cloud as well.

How can I connect my own cluster?

Here’s how you can connect an existing AWS EKS cluster to Scoutflo Deploy -

Any limitations on the “number of products” allowed to be deployed?

No. There is no limit added by Scoutflo on the “number of products” to be deployed on your cloud infrastructure.

You will have to look at the dynamic cloud cost on your AWS account, to determine the number of products you would want to self-host.

Is Scoutflo Deploy a paid product?

No. As Scoutflo Deploy is currently in the BETA phase, we will let users leverage all features for free

How can I manually create an EKS cluster?
How do I get my COSS product integrated with Scoutflo Deploy?

→ If you are listed on Scoutflo Atlas, the pre-requisites to get integrated with Scoutflo Deploy are:

i) You should have helm chart support for your applications

ii) Your helm charts should be actively supported and maintained for the latest releases of your applications and also supported on the latest EKS versions.

Why choose Kubernetes for your COSS stack?

Kubernetes is an excellent choice for open-source projects due to several reasons:

  1. Scalability and Flexibility: Kubernetes offers a highly scalable and flexible platform for managing containerized applications, which is significant for growing open-source projects.

  2. Open-Source Nature: As an open-source platform itself, Kubernetes encourages collaboration and contributions from developers worldwide. This aspect enables continuous improvement and innovation, adapting to the growing needs of various projects.

  3. Rich Ecosystem and Strong Community: Kubernetes has a robust ecosystem of associated projects, tools, and services built around it. Also, it benefits from being supported by a large, active community that contributes to its development and offers constant updates, comprehensive documentation, and user support. This makes onboarding and issue troubleshooting much more manageable.

  4. Portability and Interoperability: Kubernetes can run on numerous platforms, including public clouds, private clouds, and on-premises servers. This ensures that developers can work in a consistent environment, irrespective of where it is deployed.

  5. Enterprise Adoption: With major players like Google backing Kubernetes, it has gained widespread enterprise adoption. Utilizing such a platform for open-source projects brings in credibility and future-proofs the project to an extent.

Therefore, the features, community support, and widespread adoption make Kubernetes a popular choice for open-source projects.

Please refer to the documentation to create your own EKS cluster on your AWS account:

→ If you are not listed on Scoutflo Atlas, please email us at or fill out this form to list yourself on Scoutflo! Once listed, refer to the steps below.

If you meet the above criteria, contact us at with your helm charts, Our team would be happy to look into the same.

here
here
AWS EKS Cluster Creation Guide
contactus@scoutflo.com
contactus@scoutflo.com