What happened?
After upgrading runners to Helm 3.18.5, helm upgrade began failing schema validation for charts that reference remote JSON Schemas over HTTPS in values.schema.json
Example error:
Error: UPGRADE FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
my-app:
failing loading "https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.24.0-standalone-strict/podsecuritycontext.json": invalid file url: https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.24.0-standalone-strict/podsecuritycontext.json
The same charts and values validate and upgrade successfully with Helm 3.17.4.
What did you expect to happen?
helm upgrade should continue to accept the same values.schema.json patterns that worked in 3.17.x
How can we reproduce it (as minimally and precisely as possible)?
Chart layout (minimal):
mychart/
Chart.yaml
values.yaml
values.schema.json
values.schema.json
{
"$schema": "https://json-schema.org/draft/2019-09/schema",
"type": "object",
"properties": {
"podSecurityContext": {
"$ref": "https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.24.0-standalone-strict/podsecuritycontext.json"
}
}
}
Run
helm upgrade test ./mychart --install
Helm version
Details
This was observed on Github Actions:
Installing v3.18.5
Downloading 'v3.18.5' from 'https://get.helm.sh/'
Kubernetes version
Details
Not relevant
What happened?
After upgrading runners to Helm 3.18.5,
helm upgradebegan failing schema validation for charts that reference remote JSON Schemas over HTTPS in values.schema.jsonExample error:
The same charts and values validate and upgrade successfully with Helm 3.17.4.
What did you expect to happen?
helm upgradeshould continue to accept the same values.schema.json patterns that worked in 3.17.xHow can we reproduce it (as minimally and precisely as possible)?
Chart layout (minimal):
values.schema.json
Run
Helm version
Details
This was observed on Github Actions:Kubernetes version
Details
Not relevant