load-balancer-and-ingress-services-for-kubernetes
load-balancer-and-ingress-services-for-kubernetes copied to clipboard
vmware
[Feature Request] - Allow creation of Avi health monitors via AKO
Is your feature request related to a problem? Please describe.
Currently, to use a health monitor in AKO, it must be pre-created in the Avi controller. This poses a hindrance to automation.
Describe the solution you'd like
A way to create health monitors via AKO would alleviate the need for external custom automation, and allow me to keep more automation in one place.
A separate CR specifically for the creation of custom healthmonitors would greatly assist in providing users the ability to "keep it in Kubernetes".
Describe alternatives you've considered
Currently, to circumvent this issue, and to provide my platform users good experience, I relegated the creation/deletion of the healthmonitor to a controlscript that fires on a pool CONFIG_CREATE/CONFIG_DELETE event.
While this works, it doesn't allow for much customization, so my users are forced to use a single, pre-defined path for their healthchecks
Additional context
No response
