Skip to content

Conversation

@coolstim
Copy link

The volumeAttributesClassName attribute was already listed in the crd, but the helm chart did not pass it

@coolstim
Copy link
Author

@HoustonPutman how do we move this forward?

@coolstim
Copy link
Author

@janhoy what's the proper way to move this PR forward?

@janhoy
Copy link
Contributor

janhoy commented Jan 26, 2026

I requested a review by copilot. You can send an email to Solr dev@ list to ping a larger audience.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for the volumeAttributesClassName field in the Helm chart's data storage configuration. The field was already defined in the CRD but was not exposed through the Helm chart values.

Changes:

  • Added volumeAttributesClassName configuration option to values.yaml under dataStorage.persistent.pvc
  • Updated the SolrCloud template to pass the volumeAttributesClassName value to the PVC template spec

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
helm/solr/values.yaml Adds volumeAttributesClassName field with empty string default value under persistent PVC configuration
helm/solr/templates/solrcloud.yaml Conditionally renders volumeAttributesClassName in the PVC spec when the value is set

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +149 to +151
{{- if .Values.dataStorage.persistent.pvc.volumeAttributesClassName }}
volumeAttributesClassName: {{ .Values.dataStorage.persistent.pvc.volumeAttributesClassName | quote }}
{{- end }}
Copy link

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The volumeAttributesClassName field is being added inside a spec block that is conditionally rendered (line 139). However, the condition on line 139 only checks for capacity or storageClassName, not volumeAttributesClassName. This means if a user sets only volumeAttributesClassName without setting either storageClassName or capacity, the entire spec block will not be rendered, and volumeAttributesClassName will be silently ignored. The condition on line 139 should be updated to include .Values.dataStorage.persistent.pvc.volumeAttributesClassName in the 'or' expression.

Copilot uses AI. Check for mistakes.
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.

2 participants