source/crd: allow SRV targets with trailing dot in DNSEndpoint

[SAY-5]

Description

The DNSEndpoint CRD validator warned and skipped SRV targets that ended with a trailing dot, telling the user to remove it. Dropping the dot satisfied source/crd.go's default branch, but then Endpoint.ValidateSRVRecord rejected the endpoint in CheckEndpoint because RFC 2782 requires the target host to be an absolute FQDN with a trailing dot. The net effect: SRV records could not be created via a DNSEndpoint CRD — the user looped between both errors.

Fix

Treat SRV like CNAME in the crd.go validator. The SRV record format is <prio> <weight> <port> <host> and ValidateSRVRecord already enforces the trailing dot on the host, so crd.go should accept it and let the downstream validator decide.

Fixes

Fixes #6357

Checklist

• go test ./source/... green (including CRD suite).
• go build clean.
• gofmt clean.

Signed-off-by: SAY-5 SAY-5@users.noreply.github.com

[k8s-ci-robot]

Invalid commit message issues detected

Invalid commit messages

Keywords which can automatically close issues and hashtag(#) mentions are not allowed.

• d4858dc source/crd: allow SRV targets with trailing dot in DNSEndpoint

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ivankatliarchuk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @SAY-5. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.