-
Select Origin server based on performance metric
Ability for XC platform to select the faster member in the origin pool. If there are 3 members in the origin pool, XC selects the one with the lowest latency. The BIG-IP LB method "fastest(node)" would be the intended behavior
0
-
Service name isolation in K8s Site type
Ability to restrict access to services advertised into a K8s site type, but limiting requests from specific service names
0
-
Extended Verification certs (i.e. class 3 certificates)
Customers require class 3 certificates and currently have to provide and manage their own. Please enhance Distributed Cloud certificate services to use class 3 certificates.0
-
CE as a forward proxy to detect API calls from their internal server towards external API endpoints (egress)
The SecOps team is unaware of the types of API calls being sent to external API endpoints. These could include calls from a compressing server to outbound C2C servers. The customer is considering implementing a CE as a forward proxy to detect and ...0
-
Request tagging
A user should be able to have tags applied to requests based on request characteristics, in order to visualize those requests in a report or dashboard.0
-
Support requests that does not use SNI
We'd like to be able to communicate properly with tools that does not support SNI (here, for an example, our DNS traffic manager), so it would be great if VoltMesh was able to support these requests.0 Planned
-
Provide the CA certificates we verify an origin certificate against during the TLS handshake
In the current state of things, a customer has no way to know whether their origin server certificate will get a "pass" when setting the "Origin server verification" to "Use default trusted CA list". Although publishing this list in a formatted pa...0
-
have an alert for traffic variation above a specific threshold
Customer ****** would like an alert on DDoS attacks, one that can raise a page in PagerDuty or add a message into Slack. -
XC OpenShift Operator
Having an XC OpenShift operator that made it easier for customers to deploy CEs, do Service Discovery, etc would speed up deployments/PoCs as well as more easily selling an integration story to customers of a very commonly-deployed K8S solution.0
-
Allow the advertisement of an LB in the specific namespace in k8s
When we create an LB and choose to advertise in a CE deployed on k8s, the Service is created in the cluster using the domain configured in the LB. It would very useful to announce the LB using the Service name as the domain configured in LB and an...0