JobSetOperator is currently being created with the default name example. Using it, no new JobSets can be created, an error is shown. However, when we change JobSetOperator from example to cluster, new JobSets can be create successfully.

    Install JobSet Operator and Operand and try to create a new JobSet.

    1. Go to Software Catalog > Install cert-manager
    2. Install Job Set Operator
    3. Go to the Job Set Operator > Job Set Operator tab > Create JobSetOperator > Yaml view > Create > JSO called example will be created (video attached)
    4. Create a namespace 
    5. Create a new JobSet (example files attached)
       5a. Ex: oc apply -f jobset_policy.yaml
    

    An error is shown:  
❯ oc apply -f jobset_failure.yaml
error: resource mapping not found for name: "jobset-failure" namespace: "test-jobset" from "jobset_failure.yaml": no matches for kind "JobSet" in version "jobset.x-k8s.io/v1alpha2"
ensure CRDs are installed first

❯ oc apply -f jobset_policy.yaml
error: resource mapping not found for name: "jobset-policy" namespace: "test-jobset" from "jobset_policy.yaml": no matches for kind "JobSet" in version "jobset.x-k8s.io/v1alpha2"
ensure CRDs are installed first

    JobSet should be create successfully.

    After step 5 delete JSO example (click on the 3 dots > Delete JobSetOperator) > create a new JobSetOperator but manually change the name from example to cluster > Try to apply the same files again: 

❯ oc apply -f jobset_failure.yaml
jobset.jobset.x-k8s.io/jobset-failure created
❯ oc apply -f jobset_policy.yaml
jobset.jobset.x-k8s.io/jobset-policy created

Files are applied successfully.