Explore Curated Modules
Kubernetes
Learn moreArgo Workflows
Learn moreGitHub Actions Workflows
Learn moreGitLab CI/CD Pipelines
Learn moreBuildkite Pipelines
Learn moreGoReleaser
Learn moreAzure Pipelines
Learn moreDocker Compose
Learn moreKyverno
Learn morebitnami.com/SealedSecret
Learn morecert-manager.io
Learn morefluxcd.io
Learn moresnapshot.storage.k8s.io
Learn moreCurated Modules are vetted schemas for popular third-party tools and services like GitHub Actions, Kubernetes, and Argo CD. CUE Labs curates, tests, and maintains these modules and publishes them to our Central Registry.
This provides a trusted, secure, and efficient supply chain for your CUE configurations. You benefit from:
- Reliability: Consistent, high-quality schemas reduce errors.
- Security: Vetted modules lower the risk of vulnerabilities.
- Efficiency: Save time and effort using pre-built, maintained schemas.
You can find a complete list of our Curated Modules here.
An Official Module is a schema for a project, tool, or service that's published and maintained directly by its creators. For example, the Perses project publishes its own schemas.
These modules offer the most accurate, source-of-truth definition for configuring a tool, coming straight from upstream. Published from the official namespace, they ensure clear ownership and build trust in the schema's authenticity and correctness.
Read more about Official Modules.
Publishing your tool's CUE schemas as an Official Module via the Central Registry significantly improves your users' experience and boosts adoption. It empowers them to:
- Validate configurations early: Catch errors before they cause issues.
- Ensure consistency: Rely on a single, versioned schema, cutting down on support requests.
The Central Registry provides a robust platform with features like discoverability, documentation, dependency and version management, access control, and compliance. Plus, since CUE seamlessly supports common formats like YAML, JSON, and TOML, your users can adopt your schema without redesigning their existing systems.
Publishing modules to the Central Registry guides you through the process, step by step.
By publishing modules from your namespace, you clearly establish yourself as the official author
No sign-up is required to pull modules from the Central Registry. It's open to everyone. That said, registered users benefit from higher rate limits.