Why does Helm charts crds folder has Deployments?

[tamalsaha]

Description:
https://github.com/envoyproxy/gateway/blob/main/charts/gateway-helm/crds/gatewayapi-crds.yaml#L9195-L9440

As you can see helm crds folder has Deployment, and other types of resources. It should only have crds. What is going on here?

Repro steps:

Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Environment:

Include the environment like gateway version, envoy version and so on.

Logs:

Include the access logs and the Envoy logs.

[zirain]

this's a known issue, plan to remove in v0.6.

[arkodg]

should be fixed with #1721

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[arkodg]

should be fixed once we import upstream gateway api v1.0, which does not include any deployments or resources, relates to kubernetes-sigs/gateway-api#2401

[tamalsaha]

Thanks. But my understanding is that further changes will be needed the envoy/gateway helm chart to install the webhook deployment. Is that correct?

[arkodg]

@tamalsaha webhook based validation has been replaced by CEL based validation which is baked into the CRD schema itself.