Qovery provides comprehensive configuration options to manage every aspect of your infrastructure, from organization-level settings to individual service configurations.Documentation Index
Fetch the complete documentation index at: https://qovery-fix-azure-rg-scoped-permissions-docs.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Configuration Hierarchy
Qovery uses a hierarchical structure to organize your infrastructure:Organization
Configure organization-wide settings, access control, and integrations.Organization Settings
Basic organization configuration and settings
Members & RBAC
Manage team members, roles, and permissions
API Tokens
Generate API tokens for programmatic access
Cloud Credentials
Connect AWS, GCP, Azure, or Scaleway accounts
Git Repository Access
Configure access to GitHub, GitLab, Bitbucket
Container Registry
Connect Docker Hub, ECR, GCR, ACR, and more
Helm Repository
Add custom Helm chart repositories
SSO (SAML/OIDC)
Configure Single Sign-On authentication
Labels & Annotations
Define Kubernetes labels and annotations
Clusters
Manage Kubernetes clusters and cloud infrastructure.Clusters Configuration
Configure and manage Kubernetes clusters
Projects & Environments
Organize and manage your deployment hierarchy.Projects
Group related environments together
Environments
Configure deployment environments
Environment Variables
Manage configuration values and secrets
Services
Deploy and manage your applications and infrastructure components.Applications
Deploy containerized applications
Databases
Managed PostgreSQL, MySQL, MongoDB, Redis
Helm Charts
Deploy pre-packaged applications
Cron Jobs
Schedule recurring tasks
Lifecycle Jobs
Run one-time or event-triggered jobs
Terraform
Provision infrastructure with Terraform
Advanced Service Settings
Fine-tune service configuration
Deployment
Control how and when your services are deployed.Deployment Overview
Understand the deployment process
Deployment Pipeline
Configure staged deployments
Auto-Deploy
Automatic deployments on Git push
CI/CD Integration
Integrate with GitHub Actions, GitLab CI, etc.
Deployment Actions
Deploy, redeploy, stop, restart, rollback
Deployment Strategies
Rolling updates and recreate strategies
Deployment History
Review and rollback deployments
Deployment Statuses
Understand deployment states
Deployment Logs
Access build and runtime logs
Image Mirroring
Speed up deployments with caching
Integrations
Connect Qovery with your existing tools and cloud services.Kubernetes Providers
AWS EKS
Amazon Elastic Kubernetes Service
Google GKE
Google Kubernetes Engine
Azure AKS
Azure Kubernetes Service
Scaleway Kapsule
Scaleway Kubernetes Kapsule
Bring Your Own Kubernetes
Any Kubernetes cluster
Kubernetes Overview
Complete Kubernetes documentation
Git Providers
GitHub
GitHub and GitHub Enterprise
GitLab
GitLab cloud and self-hosted
Bitbucket
Bitbucket Cloud and Data Center
Container Registries
Docker Hub
Docker Hub registry
AWS ECR
Amazon Elastic Container Registry
GCP Artifact Registry
Google Cloud Artifact Registry
Azure ACR
Azure Container Registry
GitHub Container Registry
GitHub Container Registry
GitLab Container Registry
GitLab Container Registry
Scaleway Kapsule
Scaleway Container Registry
Generic Registry
Any OCI-compliant registry
Container Registries Overview
Complete registry documentation
CI/CD Platforms
Qovery Deploy
Zero-config builds and deployments
GitHub Actions
GitHub Actions workflows
GitHub Actions Enterprise
GitHub Enterprise self-hosted runners
GitLab CI
GitLab CI/CD pipelines
CircleCI
CircleCI workflows
Jenkins
Jenkins pipelines
Secret Managers
Doppler
Doppler secrets sync
AWS Secrets Manager
AWS Secrets Manager
Observability
Qovery Observe
Built-in observability platform
Datadog
Datadog monitoring
Kubecost
Kubernetes cost optimization
Notifications & Webhooks
Slack
Slack notifications
Webhooks
Custom webhooks for events
Other Integrations
Infrastructure as Code
Terraform, CloudFormation, and more
Helm Charts
Deploy Helm charts
API Gateway (NGINX)
NGINX API Gateway
AWS VPC Peering
AWS VPC peering configuration