Skip to content

csi-node-driver-registrar older version in newer release v26.10 #1200

Open

Description

@tonyskapunk

Describe the bug

Not sure if this is a bug or not, but found strange that the si-node-driver-registrar is using an older version in the new release v26.10.x vs previous release v26.06.x

v26.10.1

$ trident-installer-2610/tridentctl images | tail -9 | grep csi-node-driver-registrar
│                    │ registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.17.0 │

vs

v26.06.2

$ trident-installer-26062/tridentctl images | tail -9 | grep csi-node-driver-registrar
│                    │ registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.18.0 │

Environment
Provide accurate information about the environment to help us reproduce the issue.

  • Trident version: v26.10.1
  • Trident installation flags used: n/a
  • Container runtime: n/a
  • Kubernetes version: v1.36.5
  • Kubernetes orchestrator: OpenShift 5.0
  • Kubernetes enabled feature gates: n/a
  • OS: RHCOS
  • NetApp backend types: n/a
  • Other:

To Reproduce
Steps to reproduce the behavior:
Download latest release v26.10.1 issue the tricentctl images command to list the images

Expected behavior
The same or a newer version of the image.

Additional context
Add any other context about the problem here.

Activity

  1. jdm85nl commented on Nov 5, 2026

    @jdm85nl

    I've noticed that is hardcode and located here:

    26.06: https://github.com/NetApp/trident/blob/stable/v26.06/config/config.go#L285

    26.10: https://github.com/NetApp/trident/blob/stable/v26.10/config/config.go#L297

    I think this can be fixed with a 26.10.2 release?

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions