-
Allow to configure where the grafana ui reside and add a link to it in the UI.
-
**HKube micro-service**
Algo service
**Describe the bug**
1. Upon running a new job (no other jobs running in background && system is @ idle) hkube will run 2-3 instances of a algo service (spor…
-
in graphana dashboards all datasource name should be configurable
Currently datasource name in the grafana dashboard definition is always prometious.
Name should come from the values json.
-
**HKube micro-service**
Dashboard
**Describe the bug**
UI: when the Datasource is disabled It should be removed from the UI
currently, it display error: "Failed fetching dataSources collection"
to d…
-
Make tasks(algorithm run) logs more accessible
- [x] User should be able to toggle between two views, elastic and pod, pod should be disabled once the pod is down.
- [x] Logs from pod should show the…
-
**HKube micro-service**
`algorithm-builder`
**Describe the bug**
If the algorithm-builder service account has access to more than one project (namespace), i.e. `hkube` and another one, then the b…
-
**HKube micro-service**
HKUBE WEB
**Describe the bug**
from time to time the node logs are not refreshed when changing from node to node
**To Reproduce**
execute "simple" pipeline
open the job
sele…
-
**HKube micro-service**
Datasource
**Describe the bug**
Datasource -consumer concurrency is one
-
We were previously advised that when calling the python program inside a container. we should call it with a line such as:
python -u main.py 2>&1 | **tee /hkube-logs/stdout.log**
However, it turns…
-
**HKube micro-service**
Python wrapper
There was a collision between the wapper "torch" use and the algorithm implementation of the multi-process
we received the code and invastigating