allow extraVolumes and extraVolumeMounts on core#911
Conversation
Signed-off-by: Manuel Martins <Manuel.Martins@ecmwf.int>
|
Just looking around now and I believe the Pull Request |
|
Where are we with this MR? |
|
We could allow this also on portal containers since there is "setting.json" inside which could be modified that way |
|
This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days. |
|
This PR was closed because it has been stalled for 30 days with no activity. If this PR is still relevant, please re-open a new PR against main. |
|
This looked promising but was never merged nor rejected, this approach could be apply for all components, for trivy it has been just merged in #2350. |
We've deployed harbor using helm 3 on a 1.18 Kubernetes cluster:
Our storage for the registry, chartmuseum and jobservice is a NFS (ReadWriteMany) solution.
When we access the GUI, the storage gauge on the right appears with a NaN GB.
When using a ReadWriteMany storage solution, I believe this solves this issue: API api/systeminfo/volumes does't work #441
By mounting the same storage as extraVolume on the core component:
Thanks,
Manuel