Description of problem:
If the current project in scope no longer exists, even when `oc process` has no need for the current project, it will terminate with an error unless -n is specified.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. oc new-project jmp-gone
2. oc delete project jmp-gone
3. oc adm create-bootstrap-policy-file --filename=/tmp/reconcile_roles.tmp
4. oc process -f /tmp/reconcile_roles.tmp
$ oc process -f /tmp/reconcile_roles.tmp
error: unable to process template
namespaces "jmp-gone" not found
$ oc process -f /tmp/reconcile_roles.tmp -n jmp | grep jmp
(no output -- meaning no namespace was used)
The template in this example does not need the current namespace -- it should not error.
Pretty sure this is not a CLI bug since oc process is using processedtemplate API which is a namespaced API, and therefore requires a project.
correct. processing a template does run against a namespace, which is required to exist. if you want to process locally, use `oc process --local`