Plugin is removed from operator-sdk

[legal90]

Hi dear maintainers, and thank you for your work on this plugin!

I tried to use this plugin with operator-sdk v1.38.0 and it doesn't work:

$ operator-sdk init --plugins=hybrid.helm.sdk.operatorframework.io  --domain=example.com
Error: no plugin could be resolved with key "hybrid.helm.sdk.operatorframework.io"
Usage:
  operator-sdk [flags]

Examples:
The first step is to initialize your project:
    operator-sdk init [--plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>]]

<PLUGIN KEYS> is a comma-separated list of plugin keys from the following table
and <PROJECT VERSION> a supported project version for these plugins.

                             Plugin keys | Supported project versions
-----------------------------------------+----------------------------
     ansible.sdk.operatorframework.io/v1 |                          3
 deploy-image.go.kubebuilder.io/v1-alpha |                          3
                    go.kubebuilder.io/v4 |                          3
         grafana.kubebuilder.io/v1-alpha |                          3
        helm.sdk.operatorframework.io/v1 |                          3

For more specific help for the init command of a certain plugins and project version
configuration please run:
    operator-sdk init --help --plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>]

Default plugin keys: "go.kubebuilder.io/v4"
Default project version: "3"


Flags:
  -h, --help                     help for operator-sdk
      --plugins strings          plugin keys to be used for this subcommand execution
      --project-version string   project version (default "3")

FATA[0000] no plugin could be resolved with key "hybrid.helm.sdk.operatorframework.io"

And then I found that this plugin was removed from the operator-sdk upstream:
operator-framework/operator-sdk#6833

Reason:

Remove hybrid-helm v1-alpha support, due to low adoption, in favor of maintenance simplicity.

Questions

1. Will that that plugin be eventually deprecated? Does it worth for the community members to try using it for new projects?
2. If it's still alive and will be maintained - is it possible to use this plugin with latest operatior-sdk, when it's not bundled anymore? Is there a way to install it as an external plugin?

Thank you!

[joelanford]

Hey @legal90, sorry for the delay replying here!

This plugin itself has also been removed from this repo (see #381). So sorry for the inconvenience! We had no remaining active maintainers of that plugin and its presence was causing problems with the continued maintenance of this repository.

However, the library that backed that plugin is still being maintained here, so it is possible to continue building Go-based controllers that reconcile helm charts.

My recommendation would be to scaffold a standard Go-based operator using kubebuilder or operator-sdk, and then modify it to make use of helm-operator-plugins libraries as you see fit.

[artur-borys1]

Hi,
I wanted to ask if this project is still actively maintained? I can see that this repo has some activity, mainly bumping up dependencies. Last release was over half a year ago.

I'm considering using this as @joelanford suggested in the previous comment, but I just wanted to know if this project is still considered production-quality like rest of Operator Framework

I'm assuming there is no example/guide on how to integrate this with Go-based operator?

Of course I don't expect new features being added, I just want to know if I can count on this project still being maintained over next couple of months - the application I'm trying to deploy is quite large, so I want to migrate the microservices step by step from Helm to operator pattern