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

[RFE] Ability for DevOps to know the status of the pool members #3521

Open
alonsocamaro opened this issue Aug 16, 2024 · 3 comments
Open

[RFE] Ability for DevOps to know the status of the pool members #3521

alonsocamaro opened this issue Aug 16, 2024 · 3 comments

Comments

@alonsocamaro
Copy link

Title

[RFE] Ability for DevOps to know the status of the pool members

Description

DevOps who don´t have or want access to the BIG-IP console need to know the status of the pool members of the virtual servers using the kubernetes API (kubectl)

At present DevOps can only guess the list of pool members of a Service by listing of actual endpoints of the Service but that might not indicate what is the actual list of pool members and its status in the BIG-IP:

  • The VirtualServer/Transport server might have the right service name and DevOps would be unable to be aware of the typo
  • AS3 declaration might fail and not populate the list of pool members and when an AS3 declaration fails it is difficult to know what is the actual configuration in the BIG-IP
  • The BIG-IP monitor can mark down the pool members and DevOps teams don´t have a way to know this

Actual Problem

DevOps teams don´t have awareness of the status of their ingresses and they need to rely in the NetOps teams for this

Solution Proposed

A kubernetes native way to display pool member list and health status, which can be vistualized with kubectl or kubernetes UI such as the OpenShfit console

@alonsocamaro
Copy link
Author

Also, in the future this could be expanded to change the admin status of pool members but for the time being we are only requesting displaying the actual status (read-only operation)

@trinaths
Copy link
Contributor

Created [CONTCNTR-4847] for internal tracking.

@trinaths trinaths added JIRA and removed untriaged no JIRA created labels Aug 23, 2024
@alonsocamaro
Copy link
Author

I would propose that:

  • kubectl get returns the equivalent of "tmsh list ltm pool"
  • kubectl describe returns the equivalent of "tmah show ltm pool" including the stats of the pool members

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants