Upgrade Nginx Ingress Operator's Operator SDK version
OchiengEd opened this issue · 4 comments
Is your feature request related to a problem? Please describe.
Yes. The operator is dependent on packages that may be deprecated such as github.com/operator-framework/operator-sdk/pkg/k8sutil which is used to determine if the Nginx Ingress Operator is running locally or in a Kubernetes cluster.
I can put something together and create a PR.
Describe the solution you'd like
Upgrade packages removing any obsolete Golang modules and migrate to the recently released Operator SDK v1.
Describe alternatives you've considered
Replace obsolete Golang Modules and keep current Operator SDK version
Additional context
Staying on Golang modules that are no longer available may stifle developer/community contribution as they may not be able to modify, build and run the operator locally.
Hi @OchiengEd
We previously upgraded to 0.18 1f6b17f
This involved the updating of apiVersion of CRDs 1f6b17f#diff-bd2ed44f74a230a7bd9191960980cb73R1
This led to our operator being rejected by RedHats certification process because it used OpenShift 4.4 in their pipelines to certify our operator. Ultimately, we had to downgrade again: f71a8b2 .
Updating the operator-sdk is something I'd love to do, or accept a PR for, but we must remain in line with RedHats certification process.
I'll try reach out to RedHat to figure out next steps!
Sounds good. I'll reach out in the Kubernetes slack to understand the challenges with the certification process.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.