-
Notifications
You must be signed in to change notification settings - Fork 14
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
🧹 Update to go 1.18 #401
🧹 Update to go 1.18 #401
Conversation
Also update tooling: - [email protected] - [email protected] - [email protected] Fixes #243 Signed-off-by: Christian Zunker <[email protected]>
one thing that didn't work for me is
in |
Perhaps #399 helps with this PATH problem too. |
I think so because now |
Signed-off-by: Christian Zunker <[email protected]>
It looks like this PR moved us to a state where we are using go 1.18, kustomize 4.5.5, and OperatorSDK 1.21, but AFAICT go 1.18 isn't official until OperatorSDK 1.22 and OperatorSDK is still pined to kustomize v3.8.7 (even on the latest 1.22). I'm curious about what the implications are with this combination of packages that aren't presently listed as supported by OperatorSDK. This doesn't provide a lot of details: operator-framework/operator-sdk#5785 (comment) about what does/doesn't work.
^^^ Ah, it looks like the 1.21 steps were performed in PR #411 , so nevermind about those comments... |
@joelddiaz The only open topic is kustomize. We move to this version because of the Mac Silicon issue. operator-sdk 1.22.0 is also work in progress: #426 |
I realize the holdup (for OperatorSDK) is with kustomize and the lack of an arm64 binary for Mac OS. What I don't know is what changes/breaks with the move to this newer version of kustomize... |
Also update tooling:
Fixes #243
Signed-off-by: Christian Zunker [email protected]