Revision 00b7717d3564059b10ff3cdeca2290004b1f8e16 authored by Jarno Rajahalme on 08 June 2024, 11:13:30 UTC, committed by Jarno Rajahalme on 14 June 2024, 10:12:59 UTC
Clear proxy port on failure so that we'll try another random port next time. We have two failure cases for creating new redirects: - syncronous, for DNS proxy. Simply zero the proxy port in the retry loop. - asynchronous, for Envoy proxy. Clear proxy port state on revert callback. Noticed the need for this change when accidentally trying to use port 1 for Envoy when developing another feature. In this case Envoy can't bind the port, and all further tries were also trying the same port, as the proxy port was not cleared on revert. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
1 parent b30a3a9
| File | Mode | Size |
|---|---|---|
| cilium | -rw-r--r-- | 1.2 KB |
| cilium-consul.service | -rw-r--r-- | 631 bytes |
| cilium-docker.service | -rw-r--r-- | 311 bytes |
| cilium-etcd.service | -rw-r--r-- | 806 bytes |
| cilium-operator.service | -rw-r--r-- | 290 bytes |
| cilium.service | -rw-r--r-- | 313 bytes |
| cilium.service-with-docker | -rw-r--r-- | 385 bytes |
| cilium.sysusers | -rw-r--r-- | 35 bytes |
| sys-fs-bpf.mount | -rw-r--r-- | 286 bytes |
Computing file changes ...
