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
What happened?
I'm migrating a devspace.yaml from version 5.x to 6.x, and one of the major differences is the difference in specifying the deployment names.
previously the deployment name was specified via key/val, and now it's changed to directly add the name under deployments. With the new changes we run in to a deployments regex validation error. However when I verify using a custom command to echo the environment variables I can confirm that they are getting set, but the validation regex looks like it's still running on the non-templated value.
// deployment name fails foreseeably because of invalid values like $, {, } not actually expanding the PG_NAME variable
-> devspace dev
info Using namespace 'dshi'
info Using kube context 'sandbox'
fatal deployments.${PG_NAME} has to match the following regex: ^(([a-z0-9][a-z0-9\-]*[a-z0-9])|([a-z0-9]))$
// custom command properly prints env vars
-> devspace run print_pg
info Using namespace 'dshi'
info Using kube context 'sandbox'
kafka-segment-sink-pg
What did you expect to happen instead?
previously this dynamic deployment naming worked in 5.x, I'm not sure if there is plans to keep supporting this but I would expect the behaviour to be the deployment name to be templated directly and pass this regex validation. We would really appreciate this backwards compatibility because it allows us to manage our CI deployments by prepending prefixes to the pod names. Thank you!
How can we reproduce the bug? (as minimally and precisely as possible)
What happened?
I'm migrating a devspace.yaml from version 5.x to 6.x, and one of the major differences is the difference in specifying the deployment names.
6.x
vs
5.x
previously the deployment name was specified via key/val, and now it's changed to directly add the name under deployments. With the new changes we run in to a deployments regex validation error. However when I verify using a custom command to echo the environment variables I can confirm that they are getting set, but the validation regex looks like it's still running on the non-templated value.
What did you expect to happen instead?
previously this dynamic deployment naming worked in 5.x, I'm not sure if there is plans to keep supporting this but I would expect the behaviour to be the deployment name to be templated directly and pass this regex validation. We would really appreciate this backwards compatibility because it allows us to manage our CI deployments by prepending prefixes to the pod names. Thank you!
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
Local Environment:
Kubernetes Cluster:
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"28+", GitVersion:"v1.28.9-eks-036c24b", GitCommit:"f75443c988661ca0a6dfa0dc01ea82dd42d31278", GitTreeState:"clean", BuildDate:"2024-04-30T23:54:04Z", GoVersion:"go1.21.9", Compiler:"gc", Platform:"linux/arm64"}
Anything else we need to know?
The text was updated successfully, but these errors were encountered: