Externalize declarative plugin

[camilamacedo86]

What do you want to happen?

Kubebuilder introduces the plugin phase 2 implementation. One way we have a great example of how the community can leverage Kubebuilder to create your plugins would be by achieving the goal of moving the declarative plugin to its repository. See: kubernetes-sigs/kubebuilder-declarative-pattern#293

This task is to track the need to work toward this goal.

Extra Labels

No response

[aimuz]

At present, there seem to be many shortcomings in external plug-ins. For example, I want to implement a Layout plug-in. I refer to the implementation of go in the code, and cannot be well ported to external plug-ins. For now, I found that it relies on InjectConfig, but external plug-ins cannot provide

Do you have any good suggestions?

[camilamacedo86]

Hi @aimuz,

To address this need @em-r began to work on it. See: kubernetes-sigs/kubebuilder-declarative-pattern#293. The question raised on #3186 (comment) seems specific to the API and its capabilities and would fit better in a new issue. Therefore, I created this i one : #3245 (let's discuss it there)

[em-r]

@camilamacedo86 I think this is a bit similar to our discussion in #3214 (comment)
if it is worth it, I can look into adding support for injecting config into external plugins as part of #3245

[camilamacedo86]

Hi @em-r,

if it is worth it, I can look into adding support for injecting config into external plugins as part of #3245

I think we could improve to parse and inject it as well. Yes, please feel free your help is more than welcome !!! 🚀

[camilamacedo86]

We are deprecating the plugin in kubebuilder.
Also, I think we should keep the whole conversation about the new plugin externalized into the declarative project: kubernetes-sigs/kubebuilder-declarative-pattern#293