-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Support for Go version 1.21 #6722
Comments
@oceanc80, @rashmigottipati could you please confirm if this can be fixed promptly? |
FYI @everettraven @varshaprasad96 Any update on this? Facing same issue I checked the changelog here and I couldn't find the go version 1.21 PR |
We need to cut a release of ansible-operator-plugins and then bump our dependency on this and cut a release. We're in the process of upgrading our dependencies, this should happen with that automatically. |
@jberkhahn Till when can we expect the next release? |
We can see that the latest release has happened for Ansible as well as for helm.
But for ansible-operator, new release is using Go 1.21.9 . Refer below output.
can anyone explain why is this difference? |
Go 1.21 will become unsupported in August, so i opened an issue: |
Going to close this since |
Bug Report
What did you do?
ref to this issue: #6644
What did you expect to see?
Support for Go 1.21 PR to be merged for release 1.34.1 branch for ansible-operator-plugin
What did you see instead? Under which circumstances?
The ansible-operator-plugin for 1.34.1 release branch doesn't have the Bump go to 1.21 PR cherry-picked which directly could have resolved this issue Support for Go version 1.21. This issue is marked as resolved Overall, from the changelog point of view, this hasn't been resolved yet in 1.34.1 or 1.34.0 version.
Environment
Operator type: Ansible
Kubernetes cluster type:
$ operator-sdk version
: v1.34.1$ go version
(if language is Go): go1.20.14$ kubectl version
: v1.28.0Possible Solution
The ansible-operator-plugin for 1.34.1 release branch doesn't have the Bump go to 1.21 PR cherry-picked which directly can resolve this issue.
Additional context
The text was updated successfully, but these errors were encountered: