Describe your question
Out of five NAT timeouts, Config Connector ComputeRouterNAT seems to be exposing only four. Even though it is possible to change TCP TIME_WAIT Timeout using the API or a gcloud command , it is not possible to change it using Config Connector. Why is that?
The parameter is referred to as tcpTimeWaitTimeoutSec in the API and --tcp-time-wait-timeout in gcloud compute routers nats update.
Describe your question
Out of five NAT timeouts, Config Connector
ComputeRouterNATseems to be exposing only four. Even though it is possible to change TCP TIME_WAIT Timeout using the API or a gcloud command , it is not possible to change it using Config Connector. Why is that?The parameter is referred to as
tcpTimeWaitTimeoutSecin the API and--tcp-time-wait-timeoutingcloud compute routers nats update.