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
Is your feature request related to a problem? Please describe.
From the source, I notice that the Deployment generated from Wireguard CRD has hardcoded 1 as the value for spec.replicas
@jodevsa Is there a reason for it to be limited as 1? Can it scale to 2? It would be great to avoid single point of failure, by having a few more instances.
Describe the solution you'd like
Allow passing replica count through Wireguard CRD, through spec.replicas.
Describe alternatives you've considered
There seems not to be more intuitive approach than that
Additional context
The text was updated successfully, but these errors were encountered:
I manually scaled and it seems to work fine scale --replicas=2 deployment.apps/wireguard-resources-vpn-dep -n wireguard-system
Running this on EKS with NLB, even with cross-zone load balancing enabled, I could get this to work if I'm not connected to proper NLB endpoint in the same AZ where vpn server is.
after scaling (I'm using 2 AZs) it just works.
perhaps it is due to lack of proper TCP healtcheck on NLB side, hence cross-zone does not work?
Is your feature request related to a problem? Please describe.
From the source, I notice that the Deployment generated from Wireguard CRD has hardcoded 1 as the value for
spec.replicas
wireguard-operator/pkg/controllers/wireguard_controller.go
Line 682 in dbce4a8
@jodevsa Is there a reason for it to be limited as 1? Can it scale to 2? It would be great to avoid single point of failure, by having a few more instances.
Describe the solution you'd like
Allow passing replica count through
Wireguard
CRD, throughspec.replicas
.Describe alternatives you've considered
There seems not to be more intuitive approach than that
Additional context
The text was updated successfully, but these errors were encountered: