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

release: add docker image to release table #5792

Closed
awoods187 opened this issue Nov 6, 2019 · 6 comments · Fixed by #6155
Closed

release: add docker image to release table #5792

awoods187 opened this issue Nov 6, 2019 · 6 comments · Fixed by #6155

Comments

@awoods187
Copy link
Contributor

In the main docs page on releases users cannot tell that we have docker images available. At least one user didn't want to use a beta because they thought we didn't offer docker images for our alphas/betas.
image

This information is available on individual release pages:
image

We should add a docker image link to the main page.

@bdarnell also notes that our windows binaries have fallen off the main page.

There are also some ideas in this thread about how to avoid cluttering this main page.

@awoods187 awoods187 added the P-1 High priority; must be done this release label Nov 6, 2019
@awoods187
Copy link
Contributor Author

@bdarnell
Copy link
Contributor

bdarnell commented Nov 6, 2019

In addition, since helm is our most popular installation method (and is attractive for short-term testing usage even if your production installation is orchestrated differently), we should have instructions somewhere of how to run the beta with helm (i.e. edit the Image and ImageTag lines in values.yaml).

@jseldess
Copy link
Contributor

jseldess commented Nov 6, 2019

Great feedback. I'll prioritize this, but it might follow the release.

@jseldess
Copy link
Contributor

@bdarnell, we intentionally removed Windows from release notes pages in #4987 because we were getting too many incorrect assumptions about windows support, from what I remember. I believe you were involved in that decision: #4935. Have we changed our thinking in the meantime?

@bdarnell
Copy link
Contributor

The state of the windows binaries was pretty bad in 19.1. We put some work into this in 19.2 so newer releases are in better shape and we should be linking to the windows versions of 19.2+.

However, we should double-check and make sure that the binaries actually work when downloaded on to a regular windows machine. @aaron-crl mentioned that there might be issues related to the fact that we don't sign our binaries (as far as i know).

@aaron-crl
Copy link

It seems like Windows really only gets grumpy when you are trying to run unsigned drivers. I think we should still prioritize signed releases but lack of signature shouldn't be a blocker.

@jseldess jseldess moved this from In review to In progress in Education sprint 16 (1/6 - 1/17) Jan 6, 2020
jseldess added a commit that referenced this issue Jan 6, 2020
jseldess added a commit that referenced this issue Jan 7, 2020
Education sprint 13 (11/25 - 12/6) automation moved this from To do to Done Jan 7, 2020
Education sprint 14 (12/9 - 12/20) automation moved this from In review to Done Jan 7, 2020
Education sprint 16 (1/6 - 1/17) automation moved this from In progress to Done Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-doc-improvement O-product P-1 High priority; must be done this release T-missing-info
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants