-
Notifications
You must be signed in to change notification settings - Fork 195
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
Support for multiple LTM monitors when using HostGroup #3442
Comments
@thomas-cripps-fg please follow the example https://github.com/F5Networks/k8s-bigip-ctlr/blob/master/docs/config_examples/customResource/VirtualServer/HealthMonitor/monitors-virtual-server.yaml Schema should allow this. Add HostGroup to the example. Let me know the results or share your CRD to automation_toolchain_pm@f5.com |
re-opened. Let me review this with my team. |
Thanks Mark.
Issue seems to be when we have multiple virtual server CRDs all using the same virtual server and pool due to the use of HostGroup
|
@thomas-cripps-fg Please follow the example https://github.com/F5Networks/k8s-bigip-ctlr/blob/2.x-master/docs/config_examples/customResource/VirtualServer/HealthMonitor/monitors-virtual-server.yaml and share your feedback. |
Hi Trinath,
The CRD is not a problem here, we can confirm that is working.
The behaviour we see seems to relate to configuration being overwritten, appreciate AS3 is declarative but with HostGroup does that change anything?
|
@thomas-cripps-fg @trinaths lets take this conversation off GitHub and schedule a meeting to see whats going on. I will send a email. |
Thanks Mark.
…------- Removed customer name ------
|
Created [CONTCNTR-4797] for internal tracking. |
Resolved in CIS 2.18 - https://clouddocs.f5.com/containers/latest/reference/release-notes.html |
Title
Support for multiple LTM monitors on a pool when virtual server using HostGroup
Description
When deploying multiple virtual server configurations when also using HostGroup LTM monitors appear to overwrite themselves, unsure if RFE or Bug.
Actual Problem
Unable to monitor multiple applications in same backend pool as LTM monitors overwrite themselves. When a batch of VirtualServer CRDs are deployed it seems like the last CRD in the batch is the LTM monitor which persists giving the illusion of appending configuration
Solution Proposed
Allow support for multiple LTM monitors within same backend pool and the use of MinimumMonitors allows the pool not to go down
Alternatives
Unsure if anything else would work
Additional context
N/A
The text was updated successfully, but these errors were encountered: