Fixes to support Go 1.18#32611
Fixes to support Go 1.18#32611cmacknz merged 9 commits intoelastic:update-go-version-20220725210948-mainfrom
Conversation
Done to allow updating to OpenJDK 11 to ensure compatibility with the output from keytool on my local machine that used a much more recent version of OpenJDK.
The certificates were previously signed with SHA-1 which is deprecated in Go 1.18 due to being insecure.
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
|
This pull request is now in conflicts. Could you fix it? 🙏 |
This PR is branched from the Go 1.18 update branch: #32493
This includes the fixes we'll need to support Go 1.18 in beats. There were some test failures in #32493 caused by the Kafka certificates being signed with SHA-1, which is deprecated in Go 1.18 per the release notes.
I've updated the certificates used by our Kafka Docker image to use SHA-256 signatures instead of SHA-1. I also had to update the base image to Debian buster to get a version of the JDK that was compatible with the version of the Java keytool I used on my local machine to generate the certs. Otherwise Kafka will fail with
java.io.IOException: Invalid keystore format.There are still a few TODO items before I can merge this, I want to see if the tests pass first:
TODO
GODEBUG=x509sha1=1.