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
The operator should create the tunnel reliably without worrying what region is accepting new nodes.
Current Behaviour
When specifying the region with digital ocean I can only specify one region. When the region is currently not accepting any new nodes it just fails until digital ocean re-enables the zone.
Possible Solution
specify a comma separated list -region=sfo1,sfo2
Steps to Reproduce (for bugs)
Go to Digital Ocean, add a new node and check to see what region is not currently accepting new nodes and specify that region in the configuration.
Context
Your Environment
inlets-operator version, find via kubectl get deploy inlets-operator -o wide inlets/inlets-operator:0.6.6
Kubernetes distribution i.e. minikube v0.29.0., KinD v0.5.1, Docker Desktop: Rancher v2.3.2
/set title: [Feature request] Support provisioning to multiple regions for exit-servers
derekbot
changed the title
Specify more than one region for provider
[Feature request] Support provisioning to multiple regions for exit-servers
Oct 21, 2020
Thanks for the suggestion. This isn't something we've encountered as of yet.
I noticed your operator version is very old, 0.9.2 is current and you should upgrade as soon as you can.
If you're using inlets for business purposes and confidential data/credentials then you should purchase inlets PRO so that your connections are encrypted. The OSS version is configured for testing only.
Expected Behaviour
The operator should create the tunnel reliably without worrying what region is accepting new nodes.
Current Behaviour
When specifying the region with digital ocean I can only specify one region. When the region is currently not accepting any new nodes it just fails until digital ocean re-enables the zone.
Possible Solution
specify a comma separated list
-region=sfo1,sfo2
Steps to Reproduce (for bugs)
Go to Digital Ocean, add a new node and check to see what region is not currently accepting new nodes and specify that region in the configuration.
Context
Your Environment
inlets-operator version, find via
kubectl get deploy inlets-operator -o wide
inlets/inlets-operator:0.6.6
Kubernetes distribution i.e. minikube v0.29.0., KinD v0.5.1, Docker Desktop:
Rancher v2.3.2
Kubernetes version
kubectl version
:Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 18.04.4 LTS
Cloud provisioner: DigitalOcean.com
The text was updated successfully, but these errors were encountered: