-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 docs/containers for insecure releases #16034
Comments
I don't think we can remove old images, because for better or worse people may be pinned to them. I think removing old releases is very reasonable. Do you want to do a PR over on the docs site? https://github.com/envoyproxy/envoyproxy.github.io/blob/c470b304486a3ca1edbc50527c1f5ea32e2db290/_config.yml#L25 |
sort of yes - the repo is huge - need to find some disk space to do it after playing with netlify over on envoy-playground - i like it a lot - but i guess that is a separate issue |
also just thinking we may need to change envoy ci too to prevent changes being overwritten (ill check further) |
the other thing i need to proceed with this are:
|
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
description
checking the docs page, i think some of the docs relate to builds/releases for which there are known sec issues:
https://www.envoyproxy.io/docs
(also, some of the links are dead)
afaict there are also still dockerhub images with a similar issue:
https://hub.docker.com/r/envoyproxy/envoy/tags?page=1&ordering=last_updated&name=1.17
if you read the docs and look at the published images there is no way of knowing that some versions should be avoided
imho we should probably just delete all images and docs other than the latest for each minor version
The text was updated successfully, but these errors were encountered: