Page URL
https://docs.netapp.com/us-en/trident/trident-get-started/openshift-operator-deploy.html
Page title
Install Trident using OpenShift OperatorHub
Summary
Hi,
While trying to deploy Trident to our openshift cluster today we hit a snag.
The yaml file suggested for creating a trident orchestrator contains the field k8sTimeout, with that the following error occurs in the trident-operator pod:
E0401 13:07:14.596865 1 reflector.go:204] "Failed to watch" err="failed to list *v1.TridentOrchestrator: json: cannot unmarshal st
ring into Go struct field TridentOrchestratorSpec.items.spec.k8sTimeout of type int" logger="UnhandledError" reflector="pkg/mod/k8s.io/c
lient-go@v0.35.0/tools/cache/reflector.go:289" type="*v1.TridentOrchestrator"
Removing k8sTimout results in successful creation and we in the end deployed trident with NFS storage class and RWX pvc's
Public issues must not contain sensitive information
Page URL
https://docs.netapp.com/us-en/trident/trident-get-started/openshift-operator-deploy.html
Page title
Install Trident using OpenShift OperatorHub
Summary
Hi,
While trying to deploy Trident to our openshift cluster today we hit a snag.
The yaml file suggested for creating a trident orchestrator contains the field k8sTimeout, with that the following error occurs in the trident-operator pod:
E0401 13:07:14.596865 1 reflector.go:204] "Failed to watch" err="failed to list *v1.TridentOrchestrator: json: cannot unmarshal st
ring into Go struct field TridentOrchestratorSpec.items.spec.k8sTimeout of type int" logger="UnhandledError" reflector="pkg/mod/k8s.io/c
lient-go@v0.35.0/tools/cache/reflector.go:289" type="*v1.TridentOrchestrator"
Removing k8sTimout results in successful creation and we in the end deployed trident with NFS storage class and RWX pvc's
Public issues must not contain sensitive information