-
Enhancement
-
Resolution: Won't Do
-
Minor
-
None
-
None
-
None
Currently we are equally using both(our custom Resource API & operator-util) api in our code. It would be better if could use one. operator-util api is very powerful and provides lots of intergration support with k8s resources.
Idea is that we should not use third-party api internally of our code. Maybe in future we have to switch to some other API to support more funtionality. In that case we have to make lots of changes in our code.
To achive above objective we should write wrapper(Resource API) over operator-util api and use resource api in all place in our application
- is blocked by
-
KOGITO-4059 Refactor Kogito operator into internal and core component
- Resolved