Explanation

If --namespace isn't set in kyverno create exception, the namespace field will have an empty value. This PR uses the default namespace in case it isn't set.

Before the fix:

./cmd/cli/kubectl-kyverno/kubectl-kyverno create exception my-exception --policy-rules "policy,rule-1,rule-2" --all "kind=Pod,kind=Deployment,name=test-*"

apiVersion: kyverno.io/v2beta1
kind: PolicyException
metadata:
  name: my-exception
  namespace: 
spec:
  background: true
  match:
    all:
    - kinds:
        - Pod
        - Deployment
      names:
        - test-*
  exceptions:
    - policyName: policy
      ruleNames:
        - rule-1
        - rule-2

Related issue

N/A

Milestone of this PR

/milestone 1.11.1

What type of PR is this

/kind bug

Proposed Changes

Proof Manifests

./cmd/cli/kubectl-kyverno/kubectl-kyverno create exception my-exception --policy-rules "policy,rule-1,rule-2" --all "kind=Pod,kind=Deployment,name=test-*"

apiVersion: kyverno.io/v2beta1
kind: PolicyException
metadata:
  name: my-exception
  namespace: default
spec:
  background: true
  match:
    all:
    - kinds:
        - Pod
        - Deployment
      names:
        - test-*
  exceptions:
    - policyName: policy
      ruleNames:
        - rule-1
        - rule-2

Checklist

• I have read the contributing guidelines.
• I have read the PR documentation guide and followed the process including adding proof manifests to this PR.
• This is a bug fix and I have added unit tests that prove my fix is effective.
• This is a feature and I have added CLI tests that are applicable.
• My PR needs to be cherry picked to a specific release branch which is .
• My PR contains new or altered behavior to Kyverno and
  • CLI support should be added and my PR doesn't contain that functionality.
  • I have added or changed the documentation myself in an existing PR and the link is:
  • I have raised an issue in kyverno/website to track the documentation update and the link is:

Further Comments