Skip to content

Conversation

@zachsmith1
Copy link
Collaborator

@zachsmith1 zachsmith1 commented Jan 9, 2026

This pull request introduces a new Kubernetes Custom Resource Definition (CRD) for managing DNS TSIG keys (TSIGKey) within the operator. This enables users to declaratively manage TSIG keys for DNS zone transfers and updates, supporting both controller-managed and user-supplied secrets. The PR also updates documentation, IAM roles, and sample manifests to support the new resource.

Key changes:

TSIGKey CRD Implementation

  • Adds the TSIGKey CRD (api/v1alpha1/tsigkey_types.go), including its spec, status, supported algorithms, validation rules, and deepcopy methods. This resource models DNS TSIG keys and supports referencing DNS zones and secrets, as well as controller-generated secrets.
  • Generates the corresponding CRD manifest (config/crd/bases/dns.networking.miloapis.com_tsigkeys.yaml) and includes it in the CRD kustomization (config/crd/kustomization.yaml).

Ref: datum-cloud/enhancements#538

Copy link

@drewr drewr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants