Skip to content
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

Error: Unable to create magasin-dagster namespace using manual installation #40

Closed
nathanbaleeta opened this issue Feb 6, 2024 · 0 comments · Fixed by #52
Closed

Error: Unable to create magasin-dagster namespace using manual installation #40

nathanbaleeta opened this issue Feb 6, 2024 · 0 comments · Fixed by #52
Assignees
Labels
bug Something isn't working dagster installer

Comments

@nathanbaleeta
Copy link
Collaborator

nathanbaleeta commented Feb 6, 2024

Running the helm command below to create a magasin-dagster namespace returns error using manual installation.

helm install dagster magasin/dagster --namespace magasin-dagster --create-namespace

Error returned:

Error: INSTALLATION FAILED: template: dagster/templates/deployment-webserver.yaml:3:4: executing "dagster/templates/deployment-webserver.yaml" at <include "deployment-webserver" $data>: error calling include: template: dagster/templates/helpers/_deployment-webserver.tpl:36:38: executing "deployment-webserver" at <include (print $.Template.BasePath "/configmap-instance.yaml") .>: error calling include: template: dagster/templates/configmap-instance.yaml:16:12: executing "dagster/templates/configmap-instance.yaml" at <include "dagsterYaml.scheduler.daemon" .>: error calling include: template: no template "dagsterYaml.scheduler.daemon" associated with template "gotpl"

Additional context:
kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dagster installer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants