Verfication covered in the next step.
Signed-off-by: Chin-Ya Huang <chin-ya.huang@suse.com>

Updated chart and tests to allow specify Rancher custom logos persistence, persistentVolumeClaim or configMap

Starting with Rancher 2.5, the rancher pods fail with an error like

```
2020/10/13 09:34:41 [ERROR] Failed to connect to peer wss://10.42.1.13/v3/connect [local ID=10.42.2.8]: websocket: bad handshake
2020/10/13 09:34:41 [ERROR] Failed to connect to peer wss://10.42.0.11/v3/connect [local ID=10.42.2.8]: websocket: bad handshake
```

if an http proxy is configured and the default noProxy setting from the helm chart is used. This fixes this problem by adding `.svc` and `.cluster.local` to the default noProxy value.

See also for reference:
* https://github.com/rancher/k3s/issues/2176
* https://github.com/rancher/docs/issues/2725

Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>

This requires setting the docker privileged flag. Without
this the various feature charts won't run.