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
hi, I'm using Linode as my hosting provider, I recently reached the Loadbalancer threshold of 10K.
I thought about splitting the connection by DNS round-robin.
I created another ingress controller and another ingress handling the same URLs but associated with the new controller.
the problem:
based on the external DNS logs, I can see that it goes through the DNS names, and doesn't add the additional A record for the new Nginx controller[LB IP].
my current external DNS is as follows:
--metrics-address=:7979 --log-level=info --log-format=text --domain-filter=linode.sub.example.net --policy=upsert-only --provider=linode --registry=txt --interval=1m --txt-owner-id=prod-1 --txt-suffix=.prod-1 --source=ingress
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
hi, I'm using Linode as my hosting provider, I recently reached the Loadbalancer threshold of 10K.
I thought about splitting the connection by DNS round-robin.
I created another ingress controller and another ingress handling the same URLs but associated with the new controller.
the problem:
based on the external DNS logs, I can see that it goes through the DNS names, and doesn't add the additional A record for the new Nginx controller[LB IP].
my current external DNS is as follows:
--metrics-address=:7979 --log-level=info --log-format=text --domain-filter=linode.sub.example.net --policy=upsert-only --provider=linode --registry=txt --interval=1m --txt-owner-id=prod-1 --txt-suffix=.prod-1 --source=ingress
Please Advise, thanks.
Beta Was this translation helpful? Give feedback.
All reactions