NetApp
warnings.go:70 metadata.finalizers: "trident.netapp.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers
Describe the bug A clear and concise description of what the bug is.
https://github.com/NetApp/trident/blob/4513299c34b045d1d4685a60ecc8429a2b49de73/cli/k8s_client/k8s_client.go#L62 provides an error message that is also discussed in https://github.com/kubernetes/kubernetes/issues/127287
Environment Provide accurate information about the environment to help us reproduce the issue.
- Trident version: [e.g. 19.10]
- Trident installation flags used: [e.g. -d -n trident --use-custom-yaml]
- Container runtime: [e.g. Docker 19.03.1-CE]
- Kubernetes version: [e.g. 1.15.1]
- Kubernetes orchestrator: [e.g. OpenShift v3.11, Rancher v2.3.3]
- Kubernetes enabled feature gates: [e.g. CSINodeInfo]
- OS: [e.g. RHEL 7.6, Ubuntu 16.04]
- NetApp backend types: [e.g. CVS for AWS, ONTAP AFF 9.5, HCI 1.7]
- Other:
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Additional context Add any other context about the problem here.
@Dexus can you please provide more details on what the bug is ? Are you suggesting a different value for the finalizer ?
One customer mentioned that every time he is deploying Trident, a warning is issued. And that is annoying and unnecessarily unsettling.
Hi @Dexus ..what warning do you see ? Can you provide more details on the exact problem. Any additional context or log messages showing the warning would be useful. It would be great if you cab update your initial comment with more details including environment, any steps to repro, additional context etc. ?