docs: add notes distinguish from external plugin

docs/book/src/plugins/creating-plugins.md

@@ -2,12 +2,29 @@
 
 [extending-cli]: extending-cli.md
 [controller-runtime]: https://github.com/kubernetes-sigs/controller-runtime
+[creating-external-plugins]: external-plugins.md
 [operator-pattern]: https://kubernetes.io/docs/concepts/extend-kubernetes/operator
 [sdk-ansible]: https://sdk.operatorframework.io/docs/building-operators/ansible/
 [sdk-cli-pkg]: https://pkg.go.dev/github.com/operator-framework/operator-sdk/internal/cmd/operator-sdk/cli
 [sdk-helm]: https://sdk.operatorframework.io/docs/building-operators/helm/
 [sdk]: https://github.com/operator-framework/operator-sdk
 
+<aside class="note warning">
+
+<h1>Note</h1>
+
+Extending Kubebuilder can be accomplished in two primary ways:
+
+1. By re-using the existing plugins: In this approach, you use Kubebuilder as a library.
+This enables you to import existing Kubebuilder plugins and extend them, leveraging their features to build upon.
+This is particularly useful if you want to add functionalities that are closely tied with the existing Kubebuilder features.
+
+2. By Creating an External Plugin: This method allows you to create an independent, standalone plugin as a binary.
+The plugin can be written in any language and should implement an execution pattern that Kubebuilder knows how to interact with.
+You can see [Creating external plugins][creating-external-plugins] for more info.
+
+</aside>
+
 ## Overview
 
 You can extend the Kubebuilder API to create your own plugins. If [extending the CLI][extending-cli], your plugin will be implemented in your project and registered to the CLI as has been done by the [SDK][sdk] project. See its [CLI code][sdk-cli-pkg] as an example.