KIMURA Osamu

Hi enneitex, Thanks for your comment. I tried to change `TridentOrchestrator` CRD to: ```yaml apiVersion: trident.netapp.io/v1 kind: TridentOrchestrator metadata: name: trident spec: debug: false namespace: trident silenceAutosupport: true controllerPluginNodeSelector: nodetype:...

There is no `nodetype: master` label. I didn't check it. (I just follow the [sample](https://docs.netapp.com/us-en/trident/trident-get-started/kubernetes-customize-deploy.html#sample-configurations)) Even if `controllerPluginNodeSelector` is omitted, the results are same. I deleted the previous `TridentOrchestrator` and...

Unfortunately, the cluster was torn down for another test. I can't re-test with the cluster. I'm not sure about recommendation of operator placement, but most of operators are placed in...

As I stated, the cluster was torn down. No further tests were re-taken. I know there is no problem to run the Trident operator and controller on a worker node,...