eg-contrib-add-api

To add a new CRD API in Envoy Gateway, you define or modify the Go types in api/v1alpha1, apply kubebuilder markers for validation, and run the make generate workflow to produce updated CRD manifests and serialization code.

Extending an existing Envoy Gateway CRD involves updating the Go types in api/v1alpha1, adding or modifying kubebuilder validation markers, and executing code-generation scaffolding to maintain cross-CRD compatibility and serialization.

Yes, kubebuilder markers are required when modifying Envoy Gateway CRD Go types to enforce validation rules, ensure API governance, and generate the correct CRD manifests during the controller-gen workflow.

Code generation for Envoy Gateway CRD API changes works by running the make generate command, which utilizes controller-gen to process Go types and kubebuilder markers, producing updated CRD manifests and serialization files for PR-driven validation.

Yes, you can reuse shared types when adding CRD APIs in api/v1alpha1 to maintain API consistency, avoid regressions in CRD behavior, and align with Envoy Gateway's API design rules and PR governance practices.

Cross-CRD compatibility validation in Envoy Gateway is limited by shared type reuse and API design rules, requiring contributors to run make generate workflows and adhere to PR-driven validation to prevent CRD behavior regressions.