-
Show client ip when using a proxy in front of volterra
The scenario is: Client --> External proxy (like a CDN) --> Volterra gateway with HTTP load balancer --> webserver Current behavior: When looking at the HTTP load balancer request logs, the 'src ip' shows up as that of the proxy instead o...0
-
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
-
Rollback feature in case of accidental delete
Hello team, I think that it can be a good idea to have a rollback option in case someone deletes accidentally a namespace or a site. It could be beneficial in the long term cause you know, human errors are something normal, and we get 2 tickets no...
0
-
Read-Only role to see other member tickets in the same tenant
Hello team, This idea could be very beneficial for all, especially for future customers that will have a lot of users in the same tenant and they need to know if the incident was raised or not, to keep track of it and avoid duplicating unnecessary...
0
-
Support bulk credential deletes
Hit a limit in the number of vk8s credentials allowed on our account. Deleting the expired ones was a painful exercise of individually deleting each one. Please support a checkbox for multiple select - and then delete all.0
-
test
No description provided0
-
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. -
The log command needs a breakable scroll flag
'log -s vpm' or similar so that we don't have to hit Shift-g, q, up arrow, enter to see latest logs. For people that have relied on 'tail -f' in the past, it will really be helpful.0