respect envSecretRefName coming from helm values

[RafalSkolasinski]

What this PR does / why we need it:

Which issue(s) this PR fixes:

Closes #3640

Special notes for your reviewer:

In addition did some cleanup on Ansible in Core.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[RafalSkolasinski]

/test integration

[RafalSkolasinski]

All seems to work fine, I will look into adding some unit tests.

However, is it okay to use secret from

predictiveUnit:
  defaultEnvSecretRefName: < secret here >

for explainers? Internally we refer to nodes of inference graph as predictive units.

Personally, I think this is okay. I do not see need to introduce another field in helm values for explainer secrets.

[RafalSkolasinski]

integration tests passed

[axsaucedo]

It seems to have quite a few ansible and prometheus changes, is this intended?

[RafalSkolasinski]

Yes, the ansible in here needed a cleanup for quite some time. And on prometheus it is just a change of namespace in which example/docs installs it.

[axsaucedo]

Ok - the pr looks good on the explainers envSecretRef, i added a comment on the prometheus, mainly on renaming the namespace

[axsaucedo]

Looks good
/approve

[seldondev]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: axsaucedo

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

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