-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Show non-dev image installation on getting-started/install page #15730
Comments
also, the images shown in the table are wrong - it seems to be stuck on version v1.16-lates i guess we should show all of the legacy images (at least supported ones) |
related #13755 |
part of this problem is #15744 but i think it also needs to separate production/dev in the dev docs |
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. |
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. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
description
currently in the docker section on the install page it shows instructions for installing the dev image not the stable image
eg here https://www.envoyproxy.io/docs/envoy/v1.17.1/start/install#install-envoy-using-docker
whereas the getenvoy images point to stable
this is kinda inconsistent and confusing and its not clear in historical docs which image it is pointing to
i would propose to add another section for installing dev images and make sure the install section shows instructions for installing latest stable
The text was updated successfully, but these errors were encountered: