Description
Currently, when snapshots are created using Kubernetes backup tools such as Velero, Trident Protect, or others, the resulting ONTAP snapshot names follow a fixed format like snapshot-xxxxxxxxxxxxxxx. This naming convention prevents integration with NetApp tools such as BlueXP, which rely on snapshot name patterns (e.g., daily.xxx, monthly.xxx) to apply replication and retention policies as part of a 3-2-1 backup strategy.

Without meaningful snapshot names, these policies cannot be applied, limiting the usefulness of ONTAP’s native data protection features.

Proposed Feature
Introduce support for custom snapshot naming in Trident, ideally through an extension of the TridentSnapshot CRD (tridentsnapshots.trident.netapp.io). This could include:

• A new field to specify the desired snapshot name.
• Validation to ensure name compatibility with ONTAP.
• Optional templating support to dynamically generate names based on schedule type, PVC name, timestamp, etc.

This would align well with existing functionality in Trident Protect, where snapshot schedules already define granularity (e.g., hourly, daily, weekly).

Benefits

• Enables integration with NetApp BlueXP and other ONTAP-native tools
• Supports automated replication and retention policies
• Improves visibility and traceability of snapshots
• Aligns snapshot naming with organizational backup strategies

Environment

• Trident version: 25.02.1
• Kubernetes version: 1.32
• ONTAP version: 9.16.1P4

Additional Context
This feature would be especially valuable in enterprise environments with strict backup and disaster recovery policies. Let me know if a configuration example or use case diagram would help clarify the request.