With the CoreDNS Manager Operator, you can handle internal DNS directly within your Kubernetes cluster, simplifying the process and reducing infrastructure needs.
Kubebuilder validation restricts the spec.primaryNS.hostname field to a simpler hostname format, preventing the creation of more complex hostnames required for certain DNS setups.
Steps to Reproduce
Please provide detailed steps to reproduce the issue:
Create a DNSZone resource with a complex hostname.
The DNSZone "bubble-lab" is invalid: spec.primaryNS.hostname: Invalid value: "master-0.k3s": spec.primaryNS.hostname in body should match '^[a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?(\\.[a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?)*$'
Expected Behavior
The system should allow complex hostnames such as master-0.k3s for the primaryNS.hostname field to enable more detailed DNS configurations.
Actual Behavior
The current validation rules restrict the hostname format, resulting in an error when trying to apply more complex hostnames.
Environment
All environments where the CoreDNS Manager Operator is deployed.
Additional Context
The validation rules enforced by Kubebuilder do not permit the creation of more complex hostnames. For instance, the requirement is to create an NS record pointing to master-0.k3s.example.com and subsequently create an A record for it.
The Kubebuilder validation prevents the use of more complex hostnames. The objective is to create an NS record pointing to master-0.k3s.example.com and then create an A record for it.
Bug Report
Description
Kubebuilder validation restricts the spec.primaryNS.hostname field to a simpler hostname format, preventing the creation of more complex hostnames required for certain DNS setups.
Steps to Reproduce
Please provide detailed steps to reproduce the issue:
Expected Behavior
The system should allow complex hostnames such as master-0.k3s for the primaryNS.hostname field to enable more detailed DNS configurations.
Actual Behavior
The current validation rules restrict the hostname format, resulting in an error when trying to apply more complex hostnames.
Environment
All environments where the CoreDNS Manager Operator is deployed.
Additional Context
The validation rules enforced by Kubebuilder do not permit the creation of more complex hostnames. For instance, the requirement is to create an NS record pointing to master-0.k3s.example.com and subsequently create an A record for it.
Example
The Kubebuilder validation prevents the use of more complex hostnames. The objective is to create an NS record pointing to master-0.k3s.example.com and then create an A record for it.