This message was deleted.

you'd need to specify the namespace in the yaml, you can use a transformation if you don't have it set in there. what language are you using?

Nodejs. Trying to approximate the behavior if kubectl apply -n. So probably transformation it is. Imo not having namespace be a required parameter is asking for trouble. The default namespace is virtually never correct and most off the shelf resources will not want to explicitly code in a namespace

how would we define the namespace parameter in situations where the yaml has a namespace defined in it?

It should throw an error imo as kubectl does

happy to entertain a feature request here

i'd say it should probably take namespace: in the same way that helm resource does. For me, I think transforms are fine