As we try to standardize the Operator, it is highly confusing in that the Kubernetes application lifecycle tooling is itself called the "Operator Framework" with the Kubernetes Resource being called Operator itself. To prevent confusion we should rename Operator to something more idiomatic of Fabric.
As we try to standardize the Operator, it is highly confusing in that the Kubernetes application lifecycle tooling is itself called the "Operator Framework" with the Kubernetes Resource being called Operator itself. To prevent confusion we should rename Operator to something more idiomatic of Fabric.