* Cluster dashboard not rendered, fix#811
Signed-off-by: Roman <ixrock@gmail.com>
* refactoring
Signed-off-by: Roman <ixrock@gmail.com>
* actual fix
Signed-off-by: Roman <ixrock@gmail.com>
* reverted back reconnect check in cluster.activate()
Signed-off-by: Roman <ixrock@gmail.com>
* fix: cluster.activate() should not start reconnect on init (if not accessible)
Signed-off-by: Roman <ixrock@gmail.com>
* add drag and drop capabilities for the order of cluster icons on the side bar
* add type annotations for better clarity
* fix clusters staying in previously icon reordered workspaces
* add some tests to cluster-store
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* Update CRD api to use preferred version and implement v1 differences
Signed-off-by: Trevor Nichols <trevor@nichols.id.au>
* Fix unit test failure
Signed-off-by: Trevor Nichols <trevor@nichols.id.au>
* Register alternate API base URL if preferred version changes.
Signed-off-by: Trevor Nichols <trevor@nichols.id.au>
* Adjust for validation moving to the version.schema
Signed-off-by: Trevor Nichols <trevor@nichols.id.au>
* Allow for users to enabled release mode debugging by setting the env var `DEBUG` to "true"
* Adds file logging so that in production logs can still be
obtained. Those log files are limited the size and number and are rotated automatically
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* extract missing localizations from last master <- pr-merge
Signed-off-by: Roman <ixrock@gmail.com>
* fix: prevent app-crash in preferences in case of incorrect http-proxy value
Signed-off-by: Roman <ixrock@gmail.com>
* fix: don't repeat ipc-sync message to main renderer process/window when sending to frames
Signed-off-by: Roman <ixrock@gmail.com>
Signed-off-by: Roman <ixrock@gmail.com>
Co-authored-by: Sebastian Malton <sebastian@malton.name>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Lauri Nevala <lauri.nevala@gmail.com>
Co-authored-by: Alex Andreev <alex.andreev.email@gmail.com>
* adding port-forward for containers in pods
address review comments
use more idiomatic approach for async code
move some files in advance of merge conflict with Lens restructure work
* Separate the port forward links in the UI (so they don't all spin when one link is clicked)
* minor fixes
* addressed review comments (replaced <p> with <div>, moved key attribute to proper element)
* fix lint issue
* removed extraneous <div> from pod container port details
Signed-off-by: Jim Ehrismann <jehrismann@mirantis.com>
* fix format duration rounding days error
* added tests
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
Signed-off-by: Jussi Nummelin <jussi.nummelin@gmail.com>
Co-authored-by: Lauri Nevala <lauri.nevala@gmail.com>
Co-authored-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
* add LANG env with UTF-8 specified
* fix precedence of union of env objects
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* fix parseApi not accepting versions that don't start with 'v'
* add unit tests
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* fix parseApi not accepting versions that don't start with 'v'
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* Let OS allocate port number
Port availability might be tricky if some port is already in use on the
'all' interface '0.0.0.0'.
The proposed solution is to let the OS allocate the port for us using 0
as port specifier :
- first create a server instance to allocate a port number
- save port number
- close the server
- return the port number to the caller
This should be safe granted the OS doesn't reuse the port numbers on
consecutive port allocations.
see :
- about Node.js Net module : https://nodejs.org/docs/latest-v12.x/api/net.html#net_server_listen_port_host_backlog_callback
- about safety around reusing port number : https://unix.stackexchange.com/a/132524
Signed-off-by: Alexis Deruelle <alexis.deruelle@gmail.com>
