What happened?
The devspace init command fails with a fairly useless message with devspace 6.x:
fatal error rendering deployment: devspace render: exit status 1
What did you expect to happen instead?
Useful output, similar to the output of devspace v5.x:
13:36:41 [fatal] error deploying hierarchical-namespaces: the namespace from the provided object "hnc-system" does not match the namespace "default". You must pass '--namespace=hnc-system' to perform this operation.
the namespace from the provided object "hnc-system" does not match the namespace "default". You must pass '--namespace=hnc-system' to perform this operation.
the namespace from the provided object "hnc-system" does not match the namespace "default". You must pass '--namespace=hnc-system' to perform this operation.
the namespace from the provided object "hnc-system" does not match the namespace "default". You must pass '--namespace=hnc-system' to perform this operation.
the namespace from the provided object "hnc-system" does not match the namespace "default". You must pass '--namespace=hnc-system' to perform this operation.
[resource mapping not found for name: "hnc-serving-cert" namespace: "hnc-system" from "manifests/default-cm.yaml": no matches for kind "Certificate" in version "cert-manager.io/v1"
ensure CRDs are installed first, resource mapping not found for name: "hnc-selfsigned-issuer" namespace: "hnc-system" from "manifests/default-cm.yaml": no matches for kind "Issuer" in version "cert-manager.io/v1"
ensure CRDs are installed first]
Please make sure `kubectl apply` does work locally with manifest `manifests/default-cm.yaml`
How can we reproduce the bug? (as minimally and precisely as possible)
devspace upgrade --version=v6.0.0-beta.9
git clone git@github.com:kubernetes-sigs/hierarchical-namespaces.git
cd hierarchical-namespaces
make manifests
devspace init --debug
Then answer:
? Select the programming language of this project go
? How do you want to deploy this project? kubectl
? Please enter the paths to your Kubernetes manifests (comma separated, glob patterns are allowed, e.g. 'manifests/**' or 'kube/pod.yaml') [Enter to abort] manifests/default-cm.yaml
? Do you want to develop this project with DevSpace or just deploy it? [Use arrows to move, type to filter] I want to develop this project and my current working dir contains the source code
Local Environment:
- DevSpace Version: v6.0.0-beta.9
- Operating System: linux
- ARCH of the OS: AMD64
Kubernetes Cluster:
- Cloud Provider: minikube
- Kubernetes Version: client - v1.24.2, server - v1.23.8
/kind bug
What happened?
The
devspace initcommand fails with a fairly useless message with devspace 6.x:fatal error rendering deployment: devspace render: exit status 1What did you expect to happen instead?
Useful output, similar to the output of devspace v5.x:
How can we reproduce the bug? (as minimally and precisely as possible)
Then answer:
? Select the programming language of this project go
? How do you want to deploy this project? kubectl
? Please enter the paths to your Kubernetes manifests (comma separated, glob patterns are allowed, e.g. 'manifests/**' or 'kube/pod.yaml') [Enter to abort] manifests/default-cm.yaml
? Do you want to develop this project with DevSpace or just deploy it? [Use arrows to move, type to filter] I want to develop this project and my current working dir contains the source code
Local Environment:
Kubernetes Cluster:
/kind bug