Replaced kfdefs with DataScienceCluster resource and changed default ns to opendatahub

[hbelmiro]

The issue resolved by this Pull Request:

Resolves #453

Description of your changes:

Replaced kfdefs with DataScienceCluster resource and changed default ns to opendatahub

Testing instructions

In a cluster with ODH Operator with 'fast' channel installed/ODH operator version > 2.0, create the following DataScienceCluster:

$ cat <<EOF | oc apply -f -
kind: DataScienceCluster
apiVersion: datasciencecluster.opendatahub.io/v1
metadata:
  name: data-science-pipelines-operator
  namespace: opendatahub
spec:
  components:
    dashboard:
      managementState: Managed
    datasciencepipelines:
      managementState: Managed
      devFlags:
        manifests:
          - uri: https://github.com/hbelmiro/data-science-pipelines-operator/tarball/issue-453
            contextDir: config
            sourcePath: base
EOF

The data-science-pipelines-operator should start successfully.

$ oc get pods -n opendatahub   
NAME                                                              READY   STATUS    RESTARTS   AGE
data-science-pipelines-operator-controller-manager-66b79b6lzrrz   1/1     Running   0          29s
odh-dashboard-f9c79d89b-k44pf                                     2/2     Running   0          33s
odh-dashboard-f9c79d89b-wz4xb                                     2/2     Running   0          33s

Checklist

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[dsp-developers]

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483
An OCP cluster where you are logged in as cluster admin is required.

To use this image run the following:

cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/483/head
git checkout -b pullrequest 0b06b02b8398b108c0dff1319efbfb09dab70bf3
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-483"

More instructions here on how to deploy and test a Data Science Pipelines Application.

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[amadhusu]

/approve

[amadhusu]

/lgtm

[dsp-developers]

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-483

[DharmitD]

/Approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amadhusu, DharmitD

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [DharmitD]

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

[amadhusu]

/approve