DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
What happened?
When using kustomize in DevSpace, multiline strings in YAML can become incorrectly formatted, causing an error when applying the manifests.
What did you expect to happen instead?
DevSpace should produce correctly formatted YAML.
How can we reproduce the bug? (as minimally and precisely as possible)
ARCH of the OS: AMD64 | ARM64 | i386
Kubernetes Cluster:
Cloud Provider: google | aws | azure | other
Kubernetes Version: [use kubectl version]
Anything else we need to know?kustomize renders the helm chart with a multiline string | getting converted to |2, which is correct. DevSpace then attempts to apply patches and marshals / unmarshals using gopkg.in/yaml.v3. This version of go-yaml converts to 4 spaces by default and incorrectly converts |2 to |4 (a bug), which is incorrect. kubectl then throws an error.
What happened? When using kustomize in DevSpace, multiline strings in YAML can become incorrectly formatted, causing an error when applying the manifests.
What did you expect to happen instead? DevSpace should produce correctly formatted YAML.
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
manifests/vela-system/kustomization.yaml
manifests/vela-system/namespace.yaml
Local Environment:
devspace --version
]kubectl version
]Anything else we need to know?
kustomize
renders the helm chart with a multiline string|
getting converted to|2
, which is correct. DevSpace then attempts to apply patches and marshals / unmarshals using gopkg.in/yaml.v3. This version of go-yaml converts to 4 spaces by default and incorrectly converts|2
to|4
(a bug), which is incorrect.kubectl
then throws an error.