Troubleshoot Trident operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Currently the Trident Operator is not functional in Azure. It should be automagically creating PVs and associated Volumes in NetApp. There is an outstanding issue with either configuration or permissions that we need to figure out. When that's done, uncomment the function invocation in the azure clusters step. Argenx's was done manually, may need to recreate some things.
Contributor guide
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.
Research direction
The issue names no file; start at the Azure clusters step and inspect the Trident Operator configuration and permissions. Done means the operator automatically creates PVs and associated NetApp volumes in Azure, after which the function invocation can be uncommented; check whether manually created Argenx resources need recreation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100