GitOps Catalog
Distribute reusable infrastructure modules, application components, and complete environment stacks across your organization's clusters using GitOps Catalog.
What Is the GitOps Catalog?
The GitOps Catalog provides reusable templates stored in your organization's GitOps repository that enable standardized deployment of infrastructure resources and applications. Teams can deploy catalog items with custom configurations while maintaining consistency across environments.
Key Concepts
- GitOps Catalog: Reusable template stored in the
catalog/directory of your GitOps repository - Catalog Item Types: Application (applications), IaC (infrastructure), or Hybrid (both combined)
- Catalog Deployment: Instance of a catalog template deployed with custom parameter values
- Deployment Path: Location in GitOps repository where catalog generates resources
Catalog Item Types
Konstruct supports three catalog item types:
| Type | Use Cases | Technologies | Deploys To |
|---|---|---|---|
| Application | Applications, monitoring agents, platform tools | Helm, ArgoCD | Application GitOps repo |
| IaC | Cloud infrastructure, databases, networks | Terraform, Crossplane | Platform GitOps repo |
| Hybrid | Full-stack solutions combining apps and infrastructure | Both Helm and Terraform | Both repositories |
Application Catalog Items
Deploy Kubernetes applications and platform tools using Helm charts and ArgoCD Applications.
Common use cases:
- Monitoring agents (Datadog, Prometheus)
- Security tools (Cert-Manager, External Secrets)
- Developer tools (Argo Workflows, Tekton)
- Application services
Deployment location: registry/environments/<env>/<cluster>/
IaC Catalog Items
Provision cloud infrastructure resources using Terraform via Crossplane's Terraform provider.
Common use cases:
- Cloud storage (S3 buckets, Azure Storage)
- Databases (RDS, Azure SQL, Cloud SQL)
- Networking (VPCs, subnets, load balancers)
- IAM roles and policies
Deployment location: Platform GitOps repository (<platformOrg>/<projectName>-gitops)
Hybrid Catalog Items
Combine infrastructure provisioning and application deployment in a single catalog item.
Common use cases:
- Database with management application
- Monitoring infrastructure with collection agents
- Complete application stacks
- Multi-tier architectures
Deployment location: Both application and platform repositories
Getting Started
Follow these steps to start using GitOps Catalog:
- Review catalog item prerequisites
- Understand catalog item types and choose the right type
- Create your first catalog item:
- Create an Application catalog item for applications
- Create an IaC catalog item for infrastructure
- Create a Hybrid catalog item for combined deployments
- Deploy catalog items to your clusters and environments
Common Use Cases
Standardize Monitoring
Create a Datadog Application catalog item to deploy monitoring agents consistently across all clusters with environment-specific configurations.
Provision Cloud Resources
Create an S3 bucket IaC catalog item to provision storage with standardized security settings, versioning, and encryption.
Deploy Full Environments
Create a Hybrid catalog item that provisions a PostgreSQL database and deploys your application with proper connection configuration.
What's Next?
- Understand catalog item types in detail
- Review catalog item prerequisites
- Learn about catalog item annotations for Application catalog items
- View catalog item examples
- Explore dynamic environment provisioning with catalog items