Is there an existing feature request for this?
Is your feature request related to a problem or use-case? Please describe.
operator-sdk is a critical part of our build and release process. It is significantly out of date and needs to be upgraded. Unfortunately, there are several manual steps involved since operator-sdk assumes that your project has a Makefile with specific structures and attributes.
Describe the solution that you would like.
Upgrade the project to operator-sdk v1.31, iterating through each upgrade step along the way (starting with 1.18).
See https://sdk.operatorframework.io/docs/upgrading-sdk-version/
Describe alternatives you have considered.
- Stay at operator-sdk v1.17 - our tech debt continues to accumulate with compounding interest.
- Drop operator-sdk - we would have to roll our own operator build/release process.
Anything else?
Links to each upgrade step - note that we should only follow the upgrade steps for go-based operators. Changes related to Helm and Ansible-based operators do not apply:
Is there an existing feature request for this?
Is your feature request related to a problem or use-case? Please describe.
operator-sdkis a critical part of our build and release process. It is significantly out of date and needs to be upgraded. Unfortunately, there are several manual steps involved sinceoperator-sdkassumes that your project has aMakefilewith specific structures and attributes.Describe the solution that you would like.
Upgrade the project to operator-sdk v1.31, iterating through each upgrade step along the way (starting with 1.18).
See https://sdk.operatorframework.io/docs/upgrading-sdk-version/
Describe alternatives you have considered.
Anything else?
Links to each upgrade step - note that we should only follow the upgrade steps for
go-based operators. Changes related to Helm and Ansible-based operators do not apply: