The adoption of the helm hybrid operator has been very low, even in official catalogs like OperatorHub, there are only three operators, all of which are person maintained, and not organization maintained. Another bennefit is that this enables dropped the kubebuilder dependency, and we'd no longer had to generate/scaffold these files prior to and after each release of this project. This alone reduces the maintance burden to upkeep the project, as an added bonus, releases become push a tag.

And the Operator-SDK Hybrid helm plugin Incompatible with v1.36.1

    $ operator-sdk version
operator-sdk version: "v1.36.1-ocp", commit: "be22b34835cf7fbe985506936e9348233681ca3f", kubernetes version: "v1.29.0", go version: "go1.23.2", GOOS: "darwin", GOARCH: "arm64"

jitli@RedHat:~$ ../operator-sdk init --plugins=hybrid.helm.sdk.operatorframework.io --domain=hybird.com --project-version=3 --repo=github.com/example/memcached-operator

jitli@RedHat:~$ cat Dockerfile

Build the manager binary
FROM golang:1.20 as builder
WORKDIR /workspace
......    

podman build memcached-operator-48359 --arch amd64 --tag quay.io/olmqe/memcached-operator:48359-z46057z3 --authfile /tmp/ocp-48359ej3qfmn8/.dockerconfigjson 

unknown directive: toolchain\nError: building at STEP \"RUN go mod download\": while running runtime: exit status 1",

toolchain is a new feature of Go 1.21. Does OCP4.16 correspond to 1.21  Now it is 1.20

    Hybrid helm plugin has been removed in upstream, we need to remove it.