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
The k8s bigip controller sets the session value for the poolmembers of a service, but the cccl does not handle it so any kind of dynamic poolmember enabling or disabling cannot be done.
Being able to enable or disable poolmembers can be useful to avoid traffic loss in kubernetes clusters with f5 frontends and externalTrafficPolicy: Local kubernetes service as backend.
In this setup nodes may be added and removed dynamically and F5 by default sends traffic to unknown status nodes which cannot actually receive any traffic.
Being able to configure nodes as disabled and only enable them via the bigipcontroller/api when ready would help there.
The k8s bigip controller sets the session value for the poolmembers of a service, but the cccl does not handle it so any kind of dynamic poolmember enabling or disabling cannot be done.
Being able to enable or disable poolmembers can be useful to avoid traffic loss in kubernetes clusters with f5 frontends and
externalTrafficPolicy: Local
kubernetes service as backend.In this setup nodes may be added and removed dynamically and F5 by default sends traffic to unknown status nodes which cannot actually receive any traffic.
Being able to configure nodes as disabled and only enable them via the bigipcontroller/api when ready would help there.
The k8s-bigip controller (https://github.com/F5Networks/k8s-bigip-ctlr) sends following configuration data:
note the session: user-enabled value.
But the cccl in
_iapp_build_tables
https://github.com/f5devcentral/f5-cccl/blob/master/f5_cccl/resource/ltm/app_service.py#L139 does not handle the session field.Can it be considered to also handle that field by adding another column kind and extending the schema appropriately.
We have tested this with a patched cccl and it does work as expected with following patch:
The text was updated successfully, but these errors were encountered: