Skip to content

WIP: Add fsGroup annotation to set UNIX group ownership on ONTAP NAS volumes - #1190

Open
Sunnatillo wants to merge 1 commit into
NetApp:masterfrom
Nordix:feature/ontap-fsgroup-gid-annotation-master
Open

Sunnatillo wants to merge 1 commit into
NetApp:masterfrom
Nordix:feature/ontap-fsgroup-gid-annotation-master

Conversation

@Sunnatillo

@Sunnatillo Sunnatillo commented Sep 15, 2026

Copy link
Copy Markdown

Change description

Add the annotation storage.example.com/trident-fsgroup so users can set the UNIX group ID (GID) of an ONTAP NAS volume at provisioning time. The value is read from the PVC or StorageClass into the volume config, passed through the ONTAP driver's internal volume type, and applied as the NAS group ID on every volume-create call in the REST and ZAPI clients.

An empty annotation or a GID of zero means "not set" and leaves the ONTAP default unchanged. The value must be an integer between 1 and 4294967294; anything else returns an error from volume creation. REST uses int64 and ZAPI uses int, so fsgroup_utils.go provides a parser for each.

Only the ONTAP driver is affected. Mocks and existing tests are updated to pass the new argument.

Project tracking

  • This PR does not require a JIRA ticket (explain below why)

Do any added TODOs have an issue in the backlog?

Did you add unit tests? Why not?

Does this code need functional testing?

Is a code review walkthrough needed? why or why not?

Should additional test coverage be executed in addition to pre-merge?

Does this code need a note in the changelog?

Changelog

Does this code require documentation changes?

Additional Information

Add the annotation storage.example.com/trident-fsgroup so users can set
the UNIX group ID (GID) of an ONTAP NAS volume at provisioning time. The
value is read from the PVC or StorageClass into the volume config, passed
through the ONTAP driver's internal volume type, and applied as the NAS
group ID on every volume-create call in the REST and ZAPI clients.

An empty annotation or a GID of zero means "not set" and leaves the ONTAP
default unchanged. The value must be an integer between 1 and 4294967294;
anything else returns an error from volume creation. REST uses int64 and
ZAPI uses int, so fsgroup_utils.go provides a parser for each.

Only the ONTAP driver is affected. Mocks and existing tests are updated to
pass the new argument.

Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
@Sunnatillo Sunnatillo changed the title Add fsGroup annotation to set UNIX group ownership on ONTAP NAS volumes WIP: Add fsGroup annotation to set UNIX group ownership on ONTAP NAS volumes Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant