Configurable Sidecar Image Registry

[zbindenren]

Summary

The COSI sidecar image is hardcoded to gcr.io/k8s-staging-sig-storage, preventing deployment in air-gapped environments or organizations that require pulling images from private registries.

Affected Files

• helm/cosi-driver/values.yaml
• helm/cosi-driver/templates/deployment.yaml

Current Behavior

The sidecar image is hardcoded in the deployment template:

# helm/cosi-driver/templates/deployment.yaml
- name: objectstorage-driver-sidecar
  image: gcr.io/k8s-staging-sig-storage/objectstorage-sidecar@sha256:42d190db77631505e2b0fd6dc7a3186e316a57da4e449566623d259f8f9b4ff8

While the main driver image is configurable via values.yaml, the sidecar container lacks this flexibility:

# values.yaml - only main image is configurable
image:
  repository: quay.io/cloudian/cosi-driver
  tag: ""

Deployment Concerns

1. Air-Gapped Environments: Organizations without internet access cannot pull from gcr.io
2. Private Registry Requirements: Many enterprises mandate all images come from approved internal registries
3. Image Mirroring: Users who mirror images to local registries cannot override the sidecar source
4. Inconsistent Configuration: Main image is configurable, but sidecar is not

Proposed Solution

Add sidecar image configuration to values.yaml:

sidecar:
  image:
    repository: gcr.io/k8s-staging-sig-storage/objectstorage-sidecar
    digest: "sha256:42d190db77631505e2b0fd6dc7a3186e316a57da4e449566623d259f8f9b4ff8"
    # Alternatively support tag-based references
    # tag: "v20241003-v0.1.0-58-g80979e8"