Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warnings.go:70 metadata.finalizers: "trident.netapp.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers #956

Open
Dexus opened this issue Dec 3, 2024 · 2 comments
Labels

Comments

@Dexus
Copy link

Dexus commented Dec 3, 2024

Describe the bug
A clear and concise description of what the bug is.

TridentFinalizer = "trident.netapp.io"
provides an error message that is also discussed in kubernetes/kubernetes#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 Dexus added the bug label Dec 3, 2024
@sjpeeris
Copy link
Collaborator

@Dexus can you please provide more details on what the bug is ? Are you suggesting a different value for the finalizer ?

@Dexus
Copy link
Author

Dexus commented Dec 20, 2024

One customer mentioned that every time he is deploying Trident, a warning is issued. And that is annoying and unnecessarily unsettling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants