Type of question
Open question
Question
What did you do?
Using operator-sdk images as base image in our docker file
FROM quay.io/operator-framework/ansible-operator:v1.33.0
What did you expect to see? :
Want to upgrade internal Go version used by base image to 1.21.x.
What did you see instead? Under which circumstances?
Even after using latest operator-sdk image [ 1.33 ] , getting Go version as 1.20.11 .
sh-4.4$ ansible-operator version
ansible-operator version: "v1.33.0", commit: "23ab2b642f96c18070b7666a7d8f97797be2c27b", kubernetes version: "v1.27.0", go version: "go1.20.11", GOOS: "linux", GOARCH: "amd64"
Environment
Operator type: Ansible & helm
Kubernetes cluster type: OCP
$ operator-sdk version : v1.33.0
$ go version (if language is Go) : go1.20.11
$ kubectl version : v1.27.0
Additional context
In the internal security scan for my product getting some critical PSIRT raised because of the Go version used in operator-sdk base image . And to address those have to upgrade Go version to 1.21.x .
So wanted to know when new operator-sdk release/image will be available with Go version uplifted to 1.21.x