centraldashboard: removed critical vulnerabilities from centraldashboard image Fixes #7098 #7102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes:
node
because of the compliance issue(CIS_Docker_CE_v1.1.0 - 4.1) Image should be created with a non-root user
Before:
After:
Most of the remaining severities are coming from 2 packages
kubeflow/components/centraldashboard/package.json
Line 41 in d0df9b1
kubeflow/components/centraldashboard/package.json
Line 42 in d0df9b1
I tried to upgrade
@google-cloud/monitoring
to latest version and looks like it has even more vulnerabilities, so i skipped that.For
@kubernetes/client-node
looks like0.8.2
is best we can do with current node and webpack version. I tried couple of different versions, but build was breaking because of compilation issues (some names have changed in new lib version),, even after fixing those i was getting webpack issues.