Skip to content

Trident backend configuration object to support volume ownership #1079

Closed

Description

@waqar-103

Describe the bug
In Context of ontap-nas volumes, TBC objects can set unix permissions on the volume, however it cannot set volume and group ownership. In case of root squash being used fsgroup fail to apply as lchown and lchgrp commands fail to run.

Environment
Trident version: 25.10.0
Trident installation flags used: custom
Container runtime: containerd v2.1.4
Kubernetes version: v1.34.1
Kubernetes orchestrator: CCD
Kubernetes enabled feature gates: -
OS: SELS 15 SP6
NetApp backend types: ONTAP
CSI Driver fsGroupPolicy: File

To Reproduce
Steps to reproduce the behavior:

Create TBC with custom export policy which has superuser set to none.
Create pod with PVC that uses storage class that uses ontap-nas driver. Fsgroup won't be applied on the volume.
Kubelet logs will show that lchown and lchgrp failed with "operation not permitted" error

Expectation:
Trident is able to set volume ownership in case root squash is enabled.

Activity

  1. torirevilla commented on Oct 30, 2026

    @torirevilla
    Contributor

    This has been added as part of Trident release 26.10.0. See commit e80fbbb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions