Should we support application as a first class citizen and/or with namespace?

[mnkg561]

Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST

What happened: Most of the time a particular namespace represent an individual environment for a particular application(for ex: Dev, preprod, prod) and may be we should allow users to define the application as the first class citizen and then add as many number of namespaces as they want. ?

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• manager version
• Kubernetes version :

  $ kubectl version -o yaml

Other debugging information (if applicable):

- controller logs:

$ kubectl logs

[mnkg561]

if we decide to support application as a resource, We should support the configuration in a such a way that

1. Add/remove a namespace
2. Configurable cluster per namespace

This internally should call namespace controller to create/remove the namespaces but we also should support creating namespace CR directly with out defining an application. May be default to something like "default" or "playground" application.

[mnkg561]

It makes much sense to use application as first class citizen and also allow namespaces to be created with out an application.

Applications provide lot of flexibility in terms of RBAC, Namespace groups and adding/removing environments to an existing an application