-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove some vulnerabilities from go modules #4506
Comments
@EXPEbdodla Let me use this opportunity to involve you here. So far we have been steering clear of the go codebase as (at least my) assumption is that the best path forward would be to upstream the changes from your fork instead of diverging in any way. I realize we have never really discussed that though 😄 Is upstreaming also what you're working towards? |
@EXPEbdodla which version did you check for this list of Vulns? in the latest version (0.40.1) , I didn't see this package |
We are using @tokoko We can do that. But we have a backlog item for using endpoint from feature_store.yaml for transformation server calls. Once we fix that, we can do that. And we also use Datadog for our monitoring. It's added in code. Easy to resolve. |
sorry, It seems I asked a wrong person about the question.... .my bad. @EXPEbdodla. Apologize about this. |
Ok, so I cloned the repo and created docker image on master (e675cbd) 09/23. Checked vulnerabilities again. Here are the updated ones: <style> </style>
|
Most of these are coming from python3.11 image used. Can you update that to latest non-vulnerable image? Below image is from docker desktop. So after building the image you can check in vulnerabilities section if are any. |
Thank you for all the details, @brijesh-vora-sp , let me work on this. |
Description:
There are quite some vulnerabilities in feast when I build docker image of k8s materialization engine.
Seems to be all go related. Would appreciate alteast removing critical and high one's ASAP. Thanks
Possible Solution
Upgrade packages?
The text was updated successfully, but these errors were encountered: