-
Clarity on usage
Currently, if you want to understand your usages across different namespaces you need to run API queries to fully understand what apps are using what and how that is compared against your quota. This is not a very business savvy process because it...1 Planned
-
Check F5 reputation for a given IP
Feature request: check an IP reputation and Geo info through API (must have) and UI (nice to have) Issue: Customers are configuring huge Service Policies (10K+ entries) for IPs that are covered by F5 IP reputation lists (webroot, threat intelligen...0
-
allow more than 4 IP Prefix Sets per service policy
Today the console limits the user to 4 IP Prefix Sets per service policy. So for example if you have call centers in the Philippines and other countries and want to allow them through based on IP range instead of allowing the entire country you ca...1
-
unique ports for origin pool members
I have a customer that has requested the ability to have multiple origin pool servers with different ports. They are currently BIG-IP customers and so they expect this kind of ability. In their case, they want to have multiple FQDN's target the sa...0
-
F5 XC disable signatures for parameters in query or POST body
In the XC WAF the parameter context is supported but it similar to BIG-IP AWAF/ASM but to be able to stop parameter signature checks based on the parameter location will be even better!0
-
Enhancement to HTTP header processing
Currently, we only support a limited set of http header processing documented in https://docs.cloud.f5.com/docs/how-to/advanced-security/configure-http-header-processing. Customer require further details of those information which currently availa...
2
-
Simply backup all Volterra configuration (or per namespace)
I need to simply export all configuration (http load balancers, ip prefix sets, service policy, origin pool, health check, certificates, etc)0
-
Add Route feature in TCP LB
Currently the TCP LB seems not support Route feature as HTTP LB. Please add this feature so we can use the TCP LB integrate with port range to forward the traffic to specific origin pool1 Planned
-
401 errors without credentials inserted by users
The clients get many 401s because the site including static resources is protected by login but browser doesn't always send Authorization header when trying to access static resources. The origin replies with 401 and response header "www-authentic...1 Planned
-
Ability to check Pool health independent of LB health
It would be useful to add the ability to check independent pool health. Like in BIG-IP, attaching a health monitor to a pool then confirming the health check is working. The would be nice to have to ensure pool health before attaching it to a Load...1