-
-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not use Telepresence as Helm chart dependency #3833
Comments
OCI support was experimental in Helm versions prior to 3.8. What version are you using? This Helm documentation might be helpful. |
|
This documentation states:
So your dependencies should probably look like this: dependencies:
- name: telepresence-oss
repository: oci://ghcr.io/telepresenceio
version: 2.22.2
condition: enabled |
🤦 Thanks a lot. |
I've run the
|
So where does this additional "global" property come from? Telepresence has no such property. |
I have no idea. I tried doing this from scratch and I get the same error. Here are the steps:
Result:
|
Oh, I get it. In a scenario where a chart is used as a subchart, it will always be able to access global values. So helm probably adds it as an empty object. I guess our chart must accept it and any values that it may contain, although it's never used. |
The JSON schema validation implemented in Telepresence 2.22.0 had a defect: it rejected the `global` object. This object, a Helm-managed construct, facilitates the propagation of arbitrary configurations from a parent chart to its dependencies. Consequently, charts intended for dependency use must permit the presence of the `global` object. Closes #3833 Signed-off-by: Thomas Hallgren <[email protected]>
A 2.22.3 release candidate is available that fixes this problem. Please give it a spin. |
Seems it works 👍 . |
I have the following
Chart.yaml
:When I run command
helm dependencies update
orhelm dependencies build
, I get the following response:I want to have telepresence as Helm chart dependency so I can deploy it with GitOps and have Renovate watch it for automatic updates.
The text was updated successfully, but these errors were encountered: