Make config accessible for external plugin

[Eileen-Yu]

What do you want to happen?

This is the meta issue to track the feature request of making config available between KB and external plugin.

The current roadmap is:

1. Externalize the cfg struct: ✨ Externalize config struct to be available for external plugin #3554
2. Define the interface and implement the logic to pass config between KB and external plugin, there is an existing PR for this:✨ pass config between KB and external plugin #3526 (This PR will be hold until we achieved the first one)

Extra Labels

No response

[Eileen-Yu]

/assign

[camilamacedo86]

Hi @Eileen-Yu,

I think this one is done. If not could you please describe what is missing get done for we are able to close this one?

Thank you a lot for all your contributions 🥇 and help in make kubebuilder better for the community.

[Eileen-Yu]

Hi @camilamacedo86

I left a comment here to describe the bottleneck I met:
#3396 (comment)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale