NetAppDocs / NetAppDocs/trident
Cannot create orchestrator due to k8sTimeout field
@joan-ing is already working on this.
Since Apr 6, 2026.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 22
- Avg merge
- 36m
- Merged PRs (30d)
- 8
Description
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
- This issue contains no sensitive information.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.