-
Change of the "Select Type of Origin Server" pulldown in the origin server configuration
Each bullet point feels like a sentence and take time to read through. This is not necessary since the explanation is even written below. If you already know, what you need, it is easier to find in the menu just by key words. Also, I would change ...
0
-
Add TLS fingerprint as option to block bad actors in the security event actions
Add TLS fingerprint as option to block bad actors in the security event actions. Currently we can only select IP address as options and depending on the case it might be useful to block on TLS fingerprint.0
-
K8s Site site tools should be relevant to a K8s and function
Currently, K8s sites show the same site tools as full OS installed CE sites. Many of the tools interact with the OS and thus are not relevant for K8s sites. However there are additional tools which could be specific to K8s sites that would be most...0 Planned
-
distribute containers across multiple pods for 'ver'
There are current 14 containers in the 'ver-0' pod. Collectively, they require ~3000Mib. In order for the kube scheduler to place the pod a cluster node needs to have all these resources available. If these 14 containers were split across multiple...
0
-
Don't hardcode 'ves-system' namespace in vp-manager
It's currently not possible to have more than one instance of 'ves' running in a cluster. The root issue is the namespace 'ves-system' is hardcoded in vp-manager-0 during bootstrapping tasks. This is a poor practice and limits possible use cases. ...
0
-
Support service discovery of Consul servers that require a token
Volterra only supports Consul servers that use username/password to authenticate but, at least in Consul v1.9, only token-based authentication is supported. Unfortunately, this means that Volterra can't perform service discovery against Consul.0
-
Add the ability to use cloud-init when deploying VoltMesh and VoltStack on KVM
It would be useful to be able to provide the require data needed to configure networking and configure of VoltStack and VoltMesh nodes using cloud-init when initially deploying. -
Complete isolation between namespaces.
Following Zendesk ticket 509, customer would like complete isolation between namespaces across pods.0
-
Expose a service only to vk8s in a site/virtual-site
Would be good to have the possibility to expose a service via Load Balancer only to the vk8s running on a specific site/virtual site. Today it's only possible on REs, would be useful to get the same feature on CEs.0
-
Programmability to loadbalancer functions with Javascript
Can Javascript be used to influence requests and response processing in the loadbalancer to achieve programmability?0 Planned