Frequently Asked Questions (FAQ)
General Questionsβ
What is OpenChoreo?β
OpenChoreo is an open-source Internal Developer Platform (IDP) that simplifies cloud-native application development by providing developer-friendly abstractions over complex Kubernetes and cloud-native technologies.
How is OpenChoreo different from other platforms?β
OpenChoreo focuses on:
- Developer Experience: Simple abstractions without losing Kubernetes power
- Security by Default: Built-in security with cell-based architecture
- CNCF Integration: Orchestrates best-in-class cloud-native tools
- Open Source: Community-driven development with no vendor lock-in
What are the main benefits of using OpenChoreo?β
- Faster Time to Market: Deploy applications in minutes instead of days
- Reduced Complexity: Focus on business logic instead of infrastructure
- Production Ready: Enterprise-grade capabilities from day one
- Consistent Environments: Identical configurations across all stages
Getting Startedβ
What are the prerequisites for OpenChoreo?β
- Kubernetes Cluster: Version 1.24 or later
- kubectl: Configured to access your cluster
- Helm: Version 3.8 or later (for installation)
- Container Registry: For storing application images
How do I install OpenChoreo?β
Refer to the Installation Guide
Can I try OpenChoreo locally?β
Yes! The Installation Guide supports local development with k3d, as well as cloud deployments on AKS, EKS, and GKE.
What's the simplest way to deploy my first application?β
Follow Deploying your first component
Architecture & Conceptsβ
What is a "Cell" in OpenChoreo?β
A Cell is OpenChoreo's security boundary that:
- Isolates applications using Kubernetes namespaces
- Enforces network policies with Cilium
- Provides encrypted communication with mTLS
- Implements identity-based access controls
- Usually this is a Project in OpenChoreo
How does OpenChoreo handle multi-environment deployments?β
OpenChoreo uses Environment abstractions that:
- Define deployment targets (dev, staging, prod)
- Apply environment-specific configurations
- Enforce resource quotas and policies
- Enable promotion workflows between environments
What's the difference between a Project and a Component?β
- Project: A logical grouping of related components (e.g., an e-commerce platform)
- Component: An individual deployable unit (e.g., user-service, payment-api)
How does OpenChoreo integrate with existing CI/CD pipelines?β
OpenChoreo provides:
- CLI tools for integration with any CI system
- GitHub Actions for seamless GitHub workflows
- Webhooks for custom integrations
- API endpoints for programmatic access
Performance & Deploymentβ
What are the resource requirements for OpenChoreo?β
Control Plane (minimum):
- CPU: 2 cores
- Memory: 4 GB RAM (8 GB recommended with observability plane)
- Storage: 20 GB
Can OpenChoreo work with multiple clusters?β
Yes, you can setup the following patterns
- All in one cluster: Where all the planes are in a single cluster
- Combined clusters: Where a combination of planes are together spread across multiple clusters e.g. control plane separate and others together, observability plane separate and others together
- Totally seperated clusters: Where each plane has it's own cluster. Note that this is not usually for a local setup.
Licensing & Supportβ
What license does OpenChoreo use?β
OpenChoreo is licensed under the Apache 2.0 License, ensuring:
- Free commercial use
- No vendor lock-in
- Community contributions welcome
- Enterprise-friendly terms
Where can I get help?β
- Documentation: Comprehensive guides at openchoreo.dev
- Community Forum: GitHub Discussions for questions
- Chat: Real-time help on Discord
- Issues: Bug reports on GitHub Issues
Is there commercial support available?β
Not yet
How can I contribute to OpenChoreo?β
- Code Contributions: Submit pull requests on GitHub
- Documentation: Improve guides and tutorials
- Community Support: Help answer questions
- Bug Reports: File issues with detailed information
Can't find your question?
- Search our documentation
- Ask in GitHub Discussions
- Join our Discord channel