gateway api CRDs optional in stunner-gateway-operator installation

[Kariton]

in combination with other gateway api implementations it may be desirable to disable CRD installation.
my use case is in combination with envoy-gateway which ships with gateway api crds resulting in a version conflict.

i see the same issue for folks with "manually" (upstream) provisioned gateway api crds.

im happy to provide a pr.

for compatibility and to prevent unexpected breaking changes i would add the following helm default values:

gatewayApiCrds:
  enabled: true

and would update the gateway api CRD template to depend on that setting.

{{ if .Values.gatewayApiCrds.enabled }}
existing CRDs
{{ end }}

any thoughts?

greetings,
Kariton

[levaitamas]

hi @Kariton ! Thanks for taking the initiative on this indeed recurring issue. Your plan sounds great to me, but I am no Helm expert. Let me add @davidkornel to the conversation.

[Kariton]

yeah, there have been different issues and prs around this issue.
especially the gateway api CRDs are problematic in my case.

i need the stunner CRDs but not those for gateway api.
so skipping crd installation entirely is not feasible.

similar: #62