You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add gateway-icmp type monitor to probe the pod as one of CIS startup parameters
Description
Requesting a feature where the admin can specify default monitor for pod's pool set to gateway-icmp and specify it in CIS startup parameter (example: --default-pod-monitor=gateway-icmp).
Actual Problem
There is a customer using competitor solution which by default has 2 level monitor which are GSLB monitor based on HTTPS and pod-level monitor based on ICMP. Currently CIS does not support gateway-icmp monitor at pod's pool.
Solution Proposed
The admin can specify a default monitor type as one of CIS startup parameter. Example: --default-pod-monitor=gateway-icmp.
Alternatives
Another alternative is to specify the gateway-icmp monitor as an annotation in Route. This alternative is less preferred as it introduces additional external LB awareness to DevOps which is unnecessary as DevOps' scope is the cluster itself.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Title
Add gateway-icmp type monitor to probe the pod as one of CIS startup parameters
Description
Requesting a feature where the admin can specify default monitor for pod's pool set to gateway-icmp and specify it in CIS startup parameter (example: --default-pod-monitor=gateway-icmp).
Actual Problem
There is a customer using competitor solution which by default has 2 level monitor which are GSLB monitor based on HTTPS and pod-level monitor based on ICMP. Currently CIS does not support gateway-icmp monitor at pod's pool.
Solution Proposed
The admin can specify a default monitor type as one of CIS startup parameter. Example: --default-pod-monitor=gateway-icmp.
Alternatives
Another alternative is to specify the gateway-icmp monitor as an annotation in Route. This alternative is less preferred as it introduces additional external LB awareness to DevOps which is unnecessary as DevOps' scope is the cluster itself.
Additional context
N/A
The text was updated successfully, but these errors were encountered: