[bitnami/apisix] Enable admission webhook at ingress controller

[Vladimir Petr]

Name and Version

bitnami/apisix 3.3.5

What is the problem this feature will solve?

Utilising admission webhook with custom resources is vital.

Currently, when enabling APISIX ingress controller, its configuration does not enable admission webhook through kubernetes.enable_admission. As a result, the admission webhook is not enabled, although the ingress controller container as well as its service open the corresponding ports (8443 and 443, respectively). Connecting to these ports result in a connection refused error.

Furthermore, optional creating a ValidatingWebhookConfiguration for the admission webhook should be made available.

What is the feature you are proposing to solve the problem?

• Add configuration parameter kubernetes.enable_admissionin the controller's configuration, set to true by default (corresponding ports are already open)
• Add an option to create a ValidatingWebhookConfiguration for the admission webhook in the values file

What alternatives have you considered?

• Using the ingressController.extraConfig field to set the configuration parameter
• Creating a ValidatingWebhookConfiguration by means of the extraDeploy field