Skip to content
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

Closed
phlax opened this issue Mar 29, 2021 · 6 comments
Closed

Show non-dev image installation on getting-started/install page #15730

phlax opened this issue Mar 29, 2021 · 6 comments
Assignees
Labels
area/docker area/docs bug stale stalebot believes this issue/PR has not been touched recently

Comments

@phlax
Copy link
Member

phlax commented Mar 29, 2021

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

@phlax
Copy link
Member Author

phlax commented Mar 29, 2021

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)

@phlax
Copy link
Member Author

phlax commented Mar 29, 2021

related #13755

@phlax
Copy link
Member Author

phlax commented Mar 30, 2021

part of this problem is #15744 but i think it also needs to separate production/dev in the dev docs

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label May 26, 2021
@phlax phlax added no stalebot Disables stalebot from closing an issue and removed stale stalebot believes this issue/PR has not been touched recently labels May 27, 2021
@alyssawilk alyssawilk removed the no stalebot Disables stalebot from closing an issue label Oct 8, 2024
Copy link

github-actions bot commented Nov 7, 2024

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.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Nov 7, 2024
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docker area/docs bug stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants