remove kubebuilder init --plugin=helm support

[bavarianbidi]

What do you want to happen?

Feature is more a deprecation "wish" :-)

During the implementation of #4891 there was some confusion about kubebuilder init --plugin=helm.
After several discussions, Camila summarized the issue with the init implementation of the helm-plugin in this PR quite good:

Thanks for raising this — I think I now understand your point about whether we should support helm in the init interface or only in edit.

We definitely need to review this.

Technically, you can run kubebuilder init --plugins=go/v4,helm/v1-alpha1, which includes Helm during project initialization — but the Helm-specific content wouldn't be fully or properly populated at that stage.

That’s because Helm relies on the Go project being scaffolded first.

Originally, the intention was to allow us to automatically update Helm-related files using edit, since the default layout is always called in the plugin chain.

For example, if we init a project with plugins A, B, and C — when we later call create api, all those plugins will be executed in the chain automatically.

So with that in mind, it seems clearer now that having a helm init doesn't really make sense.

I think the right path is to remove the init implementation for Helm and keep only edit. Thanks again for bringing this up — I now understand the confusion you raised earlier on Slack. Would you mind opening an issue for this? And would you be interested in working on it? 🙂

I'm volunteering to implement this. As this makes #4891 more easily

Extra Labels

No response