Currently, resources created by kn-workflow gen-manifest include the namespace attribute set to default, unless the user specified a namespace explicitly.

Creating the CR and deploying the CR may not occur in the same deployment cycle.

In addition, producing manifests configured to a specific namespace (default) prevents from deploying the CR in other namespaces:

→ oc apply -f 02-configmap_mtaanalysis-props.yaml -n sonataflow-infra 
error: the namespace from the provided object "default" does not match the namespace "sonataflow-infra". You must pass '--namespace=default' to perform this operation.
→ oc create -f 02-configmap_mtaanalysis-props.yaml -n sonataflow-infra 
error: the namespace from the provided object "default" does not match the namespace "sonataflow-infra". You must pass '--namespace=default' to perform this operation.

It will be useful not to include the default namespace and postpone specifying the namespace to deploy-time, based on target env.