-
Notifications
You must be signed in to change notification settings - Fork 826
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
Updated Go to 1.14.12 #1900
Updated Go to 1.14.12 #1900
Conversation
Specifically didn't upgrade to 1.15.x due to issues with SSL certificates on fleet autoscaler webhooks.
Build Succeeded 👏 Build Id: bb28b31b-aef3-4cdd-9658-57258d05222d The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
If this is to pick up security fixes, shouldn't we rebuild and push new images (with the next release)? Otherwise, what is the point of updating the go version. Something like the supertuxcart example image, which isn't under active development isn't going to get a new version on its own any time soon. And things like the simple-game-server aren't likely to be changed but are used in all of our examples and it would be good to have users running a secured version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good, just want to resolve the question about container image versions.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
If I'm honest, I didn't do it, because it's a lot of busywork, and the security of an example images doesn't seem to me to be a huge priority? So figured, it would be taken care of on a best effort basis, rather than being a blocker for a release. SuperTuxKart should actually get updated - a new version came out a little while ago, I believe with the AI connection fixes. I don't think Xonotic has though. |
That's fair. How about filing a help-wanted issue to update the example images? Collecting the list of things that need to be rebuilt would be pretty straightforward. |
Sounds like a plan - do we restart #1261 or start a new one? 😄 |
That issue is sooooo close.... But since it's already open, I think we should just re-use it. |
How's this? |
New changes are detected. LGTM label has been removed. |
Build Failed 😱 Build Id: 50374ba1-4327-4913-9933-1b884a165ba3 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: 5474356c-1cec-40e7-bceb-d60ea3f986f9 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 318f9675-9e33-4b89-aac7-3807e2b1e304 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Great. Thanks! |
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
Security fixes really.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Specifically didn't upgrade to 1.15.x due to issues with SSL certificates on fleet autoscaler webhooks. See #1897.
I've also not incremented example image versions, since I figured this wasn't a breaking change, and the new version could be picked up as other changes happen to those images.