Use non local port for CNI Daemon

This port 50036 can be already used in the system, due
to it's in range for egress ports.

Closes-Bug: 1829188

Change-Id: Ieee291893ca342867eb408d65402a8576327ac6d
Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
This commit is contained in:
Alexey Perevalov 2019-05-20 18:11:42 +03:00 committed by Michał Dulko
parent 5ac149c7a3
commit c8a87bf2fd
3 changed files with 10 additions and 2 deletions

View File

@ -231,7 +231,7 @@ Communication
~~~~~~~~~~~~~
CNI Daemon Server is starting an HTTP server on a local network socket
(``127.0.0.1:50036`` by default). Currently server is listening for 2 API
(``127.0.0.1:5036`` by default). Currently server is listening for 2 API
calls. Both calls load the ``CNIParameters`` from the body of the call (it is
expected to be JSON).

View File

@ -34,7 +34,7 @@ daemon_opts = [
cfg.StrOpt('bind_address',
help=_('Bind address for CNI daemon HTTP server. It is '
'recommened to allow only local connections.'),
default='127.0.0.1:50036'),
default='127.0.0.1:5036'),
cfg.IntOpt('worker_num',
help=_('Maximum number of processes that will be spawned to '
'process requests from CNI driver.'),

View File

@ -0,0 +1,8 @@
---
upgrade:
- |
kuryr-daemon used to listen on port 50036, but that's a port from local
range (on Ubuntu and RHEL default range is 32768-60999). This means that
there might have been a port conflict ("address already in use"). To avoid
that the default value of ``[cni_daemon]bind_address`` option was changed
to ``127.0.0.1:5036``.