-
Notifications
You must be signed in to change notification settings - Fork 820
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
upgrade go to 1.16 and add SAN to all certs #2164
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cindy52 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build Failed 😱 Build Id: 4b8add07-128a-4281-9ba5-63be47798dfd To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: ac121d3f-3218-4904-b111-1dc2c272131d To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
In case you didn't see it:
That seems weird actually, I'm not sure what is going on there. Can you repro locally? Usually that means need to run |
Build Failed 😱 Build Id: 3f0d8eef-b354-4133-afcd-af4424753e61 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
It's weird. Every time it fails with different errors. Last time I checked it failed with |
Build Failed 😱 Build Id: 574b18ab-e747-42ba-9a79-32d3fde4a737 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: 0d083f87-d263-4d52-a4ae-5cceee0d1851 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: f9c47a63-572f-4398-a422-8f156df8c66e To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
|
Build Failed 😱 Build Id: 99e980ce-b586-48cb-b346-ecd224b2b136 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
@@ -4,7 +4,7 @@ echo "Generating certs..." | |||
echo "Email should be: [email protected]" | |||
echo "Common Name should be: agones-controller-service.agones-system.svc" | |||
openssl genrsa -out server.key 2048 | |||
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650 | |||
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650 -addext 'subjectAltName=DNS:agones-controller-service.agones-system.svc' |
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.
Aaah. That's how you do it!
Total shot in the dark, but this is the library we use: I see a similar issue here: ahmetb/gen-crd-api-reference-docs#10 Also wondering if an upgrade helps? 🤷🏻 |
I tried upgrading to the latest but still got the same err.. |
Digging into how other people fixed this on their end, looks like they found a solution here: https://github.com/knative/docs/pull/2054/files But the author does work here at Google (he's on my team 😄 ) we could always go bug him and see what he knows. It makes me feel like we're missing a reference to something somewhere. |
I saw it yesterday and even looks into his error logs in the issue: ahmetb/gen-crd-api-reference-docs#10. I believe the cause is different. For knative issue, it turns out some of the import paths are github.com instead of knative.dev, it shows in the error log he attached. I turned on detailed log as well and all import paths are agones.dev. It shows in the details of the failed build. |
Should we close this PR for now? |
Done! |
What type of PR is this?
kind cleanup
What this PR does / Why we need it:
Upgrade go version to the latest (1.16.5). Go 1.15 no longer supports Common Name based certs for HTTPS without a specific flag. This PR includes adding SAN for all related certs and updating the doc to create a cert with SAN for allocation service.
Which issue(s) this PR fixes:
Closes #1899
Closes #2024
Special notes for your reviewer: