You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I fail on creating a Zarf package for the Dagster Pipeline Orchestrator.
The Helm Chart of Dagster uses a values.schema.json file, that has a reference to the internet.
Because of that, the deployment of my Dagster Zarf package fails in my air gapped environment.
Helm seems to have a new option "skip-schema-validation" that overcomes that problem as described here: fluxcd/flux2#4992
Is it possible, that Zarf supports that flag?
Zarf v0.41.0 seems to have the required version of its dependency on Helm: #3026
Use this zarf.yaml and create a package, try to deploy it in an air gapped cluster. You must also call "zarf package create --confirm" on the air gapped cluster.
If you use that command in an environment, where it has internet access, it will work. But that's not our intended use case.
Hi,
I fail on creating a Zarf package for the Dagster Pipeline Orchestrator.
The Helm Chart of Dagster uses a values.schema.json file, that has a reference to the internet.
Because of that, the deployment of my Dagster Zarf package fails in my air gapped environment.
Helm seems to have a new option "skip-schema-validation" that overcomes that problem as described here:
fluxcd/flux2#4992
Is it possible, that Zarf supports that flag?
Zarf v0.41.0 seems to have the required version of its dependency on Helm:
#3026
Use this zarf.yaml and create a package, try to deploy it in an air gapped cluster. You must also call "zarf package create --confirm" on the air gapped cluster.
If you use that command in an environment, where it has internet access, it will work. But that's not our intended use case.
Thanks and greetings,
Josef
P.S.: I'm using Zarf v0.40.1
The text was updated successfully, but these errors were encountered: