Current behaviour

When an object is created declaratively (using the CR), some actions can still be done from the admin portal UI. This is expected currently due to THREESCALE-6051 but the User Experience is still impacted because there is no way to distinguish which resources are managed by the operator. 

For example, deploying a Tenant CR and then delete it from the admin portal UI.

Desired behaviour
If a resource is created declaratively subsequent operations/actions can't be executed/triggered from the UI i.e. the user is prevented from attempting the operation or is given a clear warning about the expected behaviour.

For example, deleting a Tenant from the admin portal UI if it has been deployed with a Tenant CR. The UI should not show the delete button. Instead it could be greyed out, not appear at all, or display a warning that the operation should be done with the operator.