Adding a namespace value to the init phase of the api.

[Daxcor69]

Feature Request

Describe the problem you need a feature to resolve.

When I deployed my first operator it didn't work. I noticed that it stuck the operator in the "default" name space. Most standard k8s "get something running" allows for a namespace designation on the cil.

Describe the solution you'd like.

operator-sdk init --plugins=ansible --domain example.com -- namespace my_kubernetes_namespace

If the namespace doesn't exist create it.

I know this value can be configured in this file

operator-framework/operator-sdk/tree/master/testdata/ansible/memcached-operator/config/default)/kustomization.yaml

I just thought this value is usually one that everyone sets.

[rashmigottipati]

/cc @theishshah

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.