Skip to content

Expose CSI sidecar images in TridentOrchestrator#1156

Open
MaxRink wants to merge 1 commit into
NetApp:masterfrom
MaxRink:tcaas/expose-trident-sidecar-images
Open

Expose CSI sidecar images in TridentOrchestrator#1156
MaxRink wants to merge 1 commit into
NetApp:masterfrom
MaxRink:tcaas/expose-trident-sidecar-images

Conversation

@MaxRink

@MaxRink MaxRink commented Jun 22, 2026

Copy link
Copy Markdown

Summary

  • add explicit TridentOrchestrator fields for CSI sidecar image overrides
  • wire the fields into operator installation and currentInstallationParams
  • expose matching Helm values and render them into the TridentOrchestrator CR
  • update the custom-image example to include sidecar image overrides

Motivation

Trident already allows the operator environment to override CSI sidecar images, but TridentOrchestrator only exposes tridentImage, autosupportImage, and imageRegistry. Operators that manage image mirrors or version automation need a CR-level way to pin sidecar image names and tags without patching the operator Deployment environment.

CR-specified sidecar images take precedence over operator environment defaults and imageRegistry rewriting. Existing behavior remains unchanged when the new fields are omitted.

Validation

  • go test ./operator/controllers/orchestrator/installer ./operator/crd/apis/netapp/v1
  • helm lint ./helm/trident-operator
  • helm template ./helm/trident-operator with all new csiSidecar*Image values set
  • YAML parse for deploy/crds/tridentorchestrator_cr_customimage.yaml and helm/trident-operator/values.yaml
  • git diff --check

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