Add kclient functions for creating deployments

[rajivnathan]

Signed-off-by: Rajiv Senthilnathan rajivsen@ca.ibm.com

What type of PR is this?
/kind feature

What does does this PR do / why we need it:
Adds the base kclient functions required for creating a Deployment that consists of a Pod with containers that map to each of the components in a Devfile. Once the devfile parsing is complete I can add the rest of the required code in a separate PR.

Which issue(s) this PR fixes:

Partially implements #2471

How to test changes / Special notes to the reviewer:

1. cd pkg/kclient
2. go test -v

Results:

=== RUN   TestCreateDeployment
=== RUN   TestCreateDeployment/Case:_Valid_deployment_name
=== RUN   TestCreateDeployment/Case:_Invalid_deployment_name
--- PASS: TestCreateDeployment (0.00s)
    --- PASS: TestCreateDeployment/Case:_Valid_deployment_name (0.00s)
    --- PASS: TestCreateDeployment/Case:_Invalid_deployment_name (0.00s)
=== RUN   TestGenerateContainerSpec
=== RUN   TestGenerateContainerSpec/#00
=== RUN   TestGenerateContainerSpec/container1
--- PASS: TestGenerateContainerSpec (0.00s)
    --- PASS: TestGenerateContainerSpec/#00 (0.00s)
    --- PASS: TestGenerateContainerSpec/container1 (0.00s)
=== RUN   TestGeneratePodSpec
=== RUN   TestGeneratePodSpec/podSpecTest
--- PASS: TestGeneratePodSpec (0.00s)
    --- PASS: TestGeneratePodSpec/podSpecTest (0.00s)
=== RUN   TestWaitAndGetPod
=== RUN   TestWaitAndGetPod/phase:_running
 ✓  Waiting for component to start [196543ns]
=== RUN   TestWaitAndGetPod/phase:_failed
 ✗  Waiting for component to start [100852ns]
=== RUN   TestWaitAndGetPod/phase:_unknown
 ✗  Waiting for component to start [103256ns]
--- PASS: TestWaitAndGetPod (0.00s)
    --- PASS: TestWaitAndGetPod/phase:_running (0.00s)
    --- PASS: TestWaitAndGetPod/phase:_failed (0.00s)
    --- PASS: TestWaitAndGetPod/phase:_unknown (0.00s)
PASS
ok  	github.com/openshift/odo/pkg/kclient	1.220s

[openshift-ci-robot]

Hi @rajivnathan. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[girishramnani]

should we make this a const?

[rajivnathan]

Added constants for the Kind and APIVersion

[girishramnani]

/ok-to-test

[girishramnani]

/ok-to-test

[rajivnathan]

/retest

[girishramnani]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: girishramnani

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 [girishramnani]

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

[rajivnathan]

/retest

[mohammedzee1000]

looks good to me
/lgtm

[mohammedzee1000]

+1

[mohammedzee1000]

/hold

[mohammedzee1000]

Sorry didnt see req for review by yusuf
/lgtm cancel
/hold cancel

[mohammedzee1000]

Once @kanchwala-yusuf takes a look we should be good to go

[kanchwala-yusuf]

/lgtm