5e773486e5
## Summary Add external-dns as a standalone self-managed application in `packages/extra/external-dns/`, allowing tenants to deploy and configure their own DNS management directly from the dashboard. ## Motivation Tenants need the ability to manage their own DNS domains with their own provider. Following the [developers guide](https://github.com/cozystack/website/pull/413), this is implemented as an extra package (like `ingress` and `seaweedfs`) using the HelmRelease-based pattern, rather than embedding it in the tenant chart. This enables multi-tenant scenarios where: - Tenant A uses Cloudflare for `domain-a.com` - Tenant B uses AWS Route53 for `domain-b.com` - Each tenant deploys and manages external-dns independently from the dashboard ## Changes - **New package**: `packages/extra/external-dns/` — standalone HelmRelease-based application - **New PackageSource**: `packages/core/platform/sources/external-dns-application.yaml` — references `system/external-dns` and `extra/external-dns` components - **Cleaned tenant chart**: removed the previously embedded `externalDns` block from `packages/apps/tenant/` ## Features - Support for 9 DNS providers: cloudflare, aws, azure, google, digitalocean, linode, ovh, exoscale, godaddy - Per-provider credential configuration with full JSON schema validation - Domain filtering via `domainFilters` - Configurable sync policy (`sync` or `upsert-only`) - Namespaced operation (`namespaced: true`) for tenant isolation - Unique `txtOwnerId` per namespace to prevent DNS record conflicts - Resource sizing via presets or explicit CPU/memory ## Usage Example Deploy from the dashboard, or via values: ```yaml # Cloudflare provider: cloudflare domainFilters: - example.com cloudflare: apiToken: "your-cloudflare-api-token" ``` ```yaml # AWS Route53 provider: aws domainFilters: - example.org aws: accessKeyId: "AKIAXXXXXXXX" secretAccessKey: "your-secret-key" region: "us-east-1" ``` ## Test plan - [ ] `helm template external-dns packages/extra/external-dns/ --set provider=cloudflare --set cloudflare.apiToken=test` renders correctly - [ ] `helm template external-dns packages/extra/external-dns/` fails (provider required) - [ ] `helm template wrong-name packages/extra/external-dns/ --set provider=cloudflare` fails (release name check) - [ ] Deploy external-dns from tenant dashboard - [ ] Verify HelmRelease is created in tenant namespace with namespaced RBAC - [ ] Create an Ingress and verify DNS record is created - [ ] Verify no conflict with global external-dns instance 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added an External DNS package for automatic DNS record management. * Support for 9 DNS providers: Cloudflare, AWS, Azure, Google, DigitalOcean, Linode, OVH, Exoscale, GoDaddy. * Helm-based deployment with namespaced/system variants and release configuration options. * Configurable synchronization policies, domain filtering, provider credentials, extra args, and resource presets. * **Documentation** * New README and schema-driven values documentation for installation and configuration. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .github | ||
| api | ||
| cmd | ||
| dashboards | ||
| docs | ||
| examples | ||
| hack | ||
| img | ||
| internal | ||
| packages | ||
| pkg | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| ADOPTERS.md | ||
| AGENTS.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTOR_LADDER.md | ||
| go.mod | ||
| go.sum | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
Cozystack
Cozystack is a free PaaS platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have Feature Requests please use the Discussion's Feature Request section.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.