You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the latest version of RKE2 forces the usage of rancher/klipper-helm:v0.8.4-build20240523 which when ran against a docker scout command has quite a few critical and high vulnerabilities. With no way of refactoring out or changing the version of the image, it provides a serious problem for hardened environments.
The documentation provides a way to override several images, but many are missing. Adding options for all images, most importantly klipper-helm, would solve this issue entirely. https://docs.rke2.io/reference/server_config#image
The only alternative I've found is to retag a newer version of the image locally, but this is messy and misleading.
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 45 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.
Currently, the latest version of RKE2 forces the usage of
rancher/klipper-helm:v0.8.4-build20240523
which when ran against a docker scout command has quite a few critical and high vulnerabilities. With no way of refactoring out or changing the version of the image, it provides a serious problem for hardened environments.The documentation provides a way to override several images, but many are missing. Adding options for all images, most importantly klipper-helm, would solve this issue entirely. https://docs.rke2.io/reference/server_config#image
The only alternative I've found is to retag a newer version of the image locally, but this is messy and misleading.
Repost of closed issue: #2160
The text was updated successfully, but these errors were encountered: