Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] - Allow creation of Avi health monitors via AKO #1100

Open
dfallert-rcd opened this issue Mar 29, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@dfallert-rcd
Copy link

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

@dfallert-rcd dfallert-rcd added the enhancement New feature or request label Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant