Datasets:
Several Gateway API CRD validation markers are attached to types that do not express the intended schema, and the InferencePool generated CRD is missing bounds for its endpoint selector map. Invalid port values or empty and oversized selector maps can therefore pass schema validation, while regenerated artifacts may drift between the core API and the inference extension. Correct the marker/type contract and ensure CRD generation validates both repositories without changing valid resources.