Add controller-runtime option to code section

enhancements/node-tuning/pao-in-nto.md

@@ -103,8 +103,8 @@ that can be used to
 PAO code would be moved into the NTO repository as a separate controller. The Telco team would keep ownership as it has the necessary domain knowledge needed to implement the low latency tuning.
 
 The code currently uses Operator SDK libraries in some of the tests and this might need to be changed.
-Migrating the use of these libaries to [library-go](https://github.com/openshift/library-go)
-would be one of the options.
+Migrating the use of these libaries to [library-go](https://github.com/openshift/library-go) or stripping them to [controller-runtime](https://github.com/kubernetes-sigs/controller-runtime)
+would be options in hand.
 
 PAO also implements a [conversion webhook](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion)
 The hook is currently installed via OLM mechanisms and this might need to be reimplemented or changed to use whatever CVO or ART support.