-
Notifications
You must be signed in to change notification settings - Fork 31
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
Move to go1.19 #96
Move to go1.19 #96
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
Moving away from the go-toolset image as it often lays some versions behind |
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #96 +/- ##
=======================================
Coverage 41.54% 41.54%
=======================================
Files 29 29
Lines 1993 1993
=======================================
Hits 828 828
Misses 1127 1127
Partials 38 38
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
@@ -1,8 +1,7 @@ | |||
# Build the manager binary | |||
FROM registry.access.redhat.com/ubi9/go-toolset:1.18.4 as builder | |||
FROM docker.io/library/golang:1.19 as builder |
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.
is this intentional ? we should find go1.19 go-toolset from redhat registry right ?
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.
yes it is intentional, ubi's go-toolset often lies behind in terms of go version so we want something more up to date.
This is for the upstream/community build, so using golang:1.19
is fine (we actually do the same already for a while in flowlogs-pipeline); the Dockerfile for downstream is different and uses images from redhat registry.
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.
pls restore changes to bpf_bpfel/g.go files no need to merge them
I have a question about new builder image
is that considered secure from RH prespective ? did u check to see if there are other alternatives ? |
it wasn't a manual edit, it's a new format from |
/lgtm |
* Move to go1.19 * Fix go1.19 breaking cvhanges * Still allow building with 1.18 * revert space changes on autogen files
No description provided.