### Environment detail -

EKS v1.29
Emissary-ingress app v3.9.1
Emissary-ingress chart v8.9.1

### Issue detail -

We are trying to install emissary-ingress chart from scratch on EKS cluster, but the installation fails every single time. For every installation failure so far, we are seeing either of the following 2 errors intermittently -

Error#1-
Error: validation failed: unable to recognize "": no matches for kind "Module" in version "getambassador.io/v3alpha1"

In this case, the chart doesn't get installed at all and no emissary-ingress related resources are created.

Error#2-
Error: release ambassador failed: conversion webhook for getambassador.io/v3alpha1, Kind=Module failed: Post "https://emissary-apiext.emissary-system.svc:443/?timeout=30s": no endpoints available for service "emissary-apiext"

In this case, it seems the resources are partially created. At least the apiext pods in emissary-system namespace are up and running. Still the installation complains that endpoints are not available for the same.
Wondering if we may increase this 30 second timeout somewhere in CRD definition to work around this error.

Please advise how to get rid of these errors to get a successful installation.

On a different note, is there any option available to disable this apiext stuff altogether if we want to use v3alpha1 for all resources and don't need any conversion?