fix(kubeapiserver): validate group resource strings to support groups with periods #33647
+36
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Improves the parsing of "group resource" strings when using
kubernetes_resources_annotations_as_tags
/kubernetes_resources_labels_as_tags
to support groups that contain periods. The updated code uses Kubernetes' own validations to ensure that the resource and group are RFC1123-compliant Labels and Subdomains, respectively.Fixes #33646
Motivation
The current validation logic requires that the key will contain only one period, meaning it's not currently possible to specify resources whose groups contain periods as is common with CRDs.
Describe how you validated your changes
Updated tests and included additional negative tests for invalid entries.
Possible Drawbacks / Trade-offs
None known