feat: Option to have devspaces operator create namespace instead of p…

[tolusha]

…roject on OCP

What does this PR do?

Option to have devspaces operator create namespace instead of project on OCP

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-9951

How to test this PR?

1. Create a project template

apiVersion: template.openshift.io/v1
kind: Template
metadata:
  name: project-request
  namespace: openshift-config
objects:
  - apiVersion: project.openshift.io/v1
    kind: Project
    metadata:
      name: ${PROJECT_NAME}
  - apiVersion: v1
    kind: ConfigMap
    metadata:
      name: welcome-config-map
      namespace: '${PROJECT_NAME}'
    data:
      welcome_message: Welcome to your new OpenShift Project
parameters:
- name: PROJECT_NAME
- name: PROJECT_DISPLAYNAME
- name: PROJECT_DESCRIPTION
- name: PROJECT_ADMIN
- name: PROJECT_REQUESTING_USER

2. Update project config

apiVersion: config.openshift.io/v1
kind: Project
metadata:
  name: cluster
spec:
  projectRequestTemplate:
    name: project-request

3. Deploy Eclipse Che with a custom che image and configured CheCluster CR

spec:
  components:
    cheServer:
      extraProperties:
        CHE_INFRA_OPENSHIFT__KUBERNETES_NAMESPACE_FACTORY: "true"

4. Create any project in OpenShift, ensure that configmap welcome-config-map is created as well
5. Login in into Eclipse Che
6. Check a user project, ensure that welcome-config-map is NOT created.

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Release Notes

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tolusha

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-server:pr-973

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/cheServer/deployment", "value": {containers: [{image: "quay.io/eclipse/che-server:pr-973", name: che}]}}]"

[openshift-ci]

@tolusha: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v19-github-no-pat-oauth-flow-raw-devfile-url	ff388e1	link	true	/test v19-github-no-pat-oauth-flow-raw-devfile-url
ci/prow/v19-github-no-pat-oauth-flow	ff388e1	link	true	/test v19-github-no-pat-oauth-flow
ci/prow/v19-gitea-no-pat-oauth-flow	ff388e1	link	true	/test v19-gitea-no-pat-oauth-flow
ci/prow/v19-che-smoke-test	ff388e1	link	true	/test v19-che-smoke-test
ci/prow/v19-github-no-pat-oauth-flow-ssh-url	ff388e1	link	true	/test v19-github-no-pat-oauth-flow-ssh-url

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.