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

Updated Go to 1.14.12 #1900

Merged
merged 2 commits into from
Nov 17, 2020

Conversation

markmandel
Copy link
Collaborator

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind breaking
/kind bug

/kind cleanup

/kind documentation
/kind feature
/kind hotfix

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.

Specifically didn't upgrade to 1.15.x due to issues with SSL
certificates on fleet autoscaler webhooks.
@markmandel markmandel added kind/cleanup Refactoring code, fixing up documentation, etc area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. area/security Issues pertaining to security labels Nov 16, 2020
@google-cla google-cla bot added the cla: yes label Nov 16, 2020
@agones-bot
Copy link
Collaborator

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:

  • git fetch https://github.com/googleforgames/agones.git pull/1900/head:pr_1900 && git checkout pr_1900
  • helm install ./install/helm/agones --namespace agones-system --name agones --set agones.image.tag=1.11.0-85b26c1

@roberthbailey
Copy link
Member

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.

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.

Copy link
Member

@roberthbailey roberthbailey left a 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.

@google-oss-robot
Copy link

[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:
  • OWNERS [markmandel,roberthbailey]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@markmandel
Copy link
Collaborator Author

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.

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.

@roberthbailey
Copy link
Member

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.

@markmandel
Copy link
Collaborator Author

Sounds like a plan - do we restart #1261 or start a new one? 😄

@roberthbailey
Copy link
Member

That issue is sooooo close.... But since it's already open, I think we should just re-use it.

@markmandel
Copy link
Collaborator Author

How's this?
#1261 (comment)

@google-oss-robot
Copy link

New changes are detected. LGTM label has been removed.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 50374ba1-4327-4913-9933-1b884a165ba3

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 5474356c-1cec-40e7-bceb-d60ea3f986f9

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

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:

  • git fetch https://github.com/googleforgames/agones.git pull/1900/head:pr_1900 && git checkout pr_1900
  • helm install ./install/helm/agones --namespace agones-system --name agones --set agones.image.tag=1.11.0-a6c7e59

@roberthbailey
Copy link
Member

How's this?
#1261 (comment)

Great. Thanks!

@roberthbailey roberthbailey merged commit 42b8660 into googleforgames:master Nov 17, 2020
@markmandel markmandel deleted the cleanup/go-1.14.12 branch November 18, 2020 00:12
@markmandel markmandel added this to the 1.11.0 milestone Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. area/security Issues pertaining to security cla: yes kind/cleanup Refactoring code, fixing up documentation, etc size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants