Move helm chart version to strict SemVer 2

[ed-boykin]

Helm v3 requires strict SemVer2 versioning. In particular OCI repositories will not support the current versioning scheme used by the azurefile-csi-driver. ex: v1.29.5.

Security requirements may require cached pull-through on charts, or for 3rd party charts to be stored in private OCI repos.

Would like to see the Chart.yaml version field use proper SemVer2 by removing the 'v', ex: version: 1.29.5 instead of version: v.1.29.5

Helm Chart versioning
SemVer2

[andyzhangx]

@ed-boykin
there are appVersion and version fields, which one should not have v? and for compatibility concern, we won't do that for existing v1.30 or earlier versions, we could fix is in v1.31 or later version.

azurefile-csi-driver/charts/v1.30.2/azurefile-csi-driver/Chart.yaml

Lines 2 to 5 in a628f71

	appVersion: v1.30.2
	description: Azure File Container Storage Interface (CSI) Storage Plugin
	name: azurefile-csi-driver
	version: v1.30.2

[ed-boykin]

The 'version' field is the important one. This is used by helm tools especially when packaging the chart and when pushing to an OCI repo.
Charts and Versioning

Understood about not fixing prior versions.

[andyzhangx]

we could only fix this from 1.31

[ed-boykin]

That would be ok and VERY helpful. Thanks.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ed-boykin]

/remove-lifecycle stale