Conversation
ThoSap
changed the title
hostname JSON Schema format
alexlanz
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related to base PR #36
As Quarkus now uses Fabric8 Kubernetes Client v7.5.X, we can use the new CRD Generator v2 API
io.fabric8.crdv2.generator.v1.SchemaCustomizerto tell Kubernetes resource reference fieldsnamespaceandname, and thehostfield in theClusterConnectionSpecto use JSON Schemaformat: hostname.Kubernetes uses RFC 1123 to validate resource names, so our CRD should also validate that before a malformed resource ref is used in a CRD Spec and applied to the cluster, which then fails in the reconciler.
https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names
Related to comment #2 (comment)
