chaos-mesh: Error while installaing chaos-mesh: "tls: failed to find any PEM data in certificate input"

Bug Report

What version of Kubernetes are you using?

Client Version: v1.15.3
Server Version: v1.12.8

What did you do?

kind delete cluster
cd chaos-mesh
hack/kind-cluster-build.sh
kubectl apply -f manifests/
helm install chaos-mesh/helm/chaos-mesh --name=chaos-mesh --namespace=chaos-testing --set chaosDaemon.runtime=containerd --set chaosDaemon.socketPath=/run/containerd/containerd.sock

What did you expect to see?

All PODs in chaos-testing namespace to be up and running

What did you see instead?

 $ helm install helm/chaos-mesh --name=chaos-mesh --namespace=chaos-testing --set chaosDaemon.runtime=containerd --set chaosDaemon.socketPath=/run/containerd/containerd.sock
NAME:   chaos-mesh
LAST DEPLOYED: Mon Feb 10 16:00:45 2020
NAMESPACE: chaos-testing
STATUS: DEPLOYED

RESOURCES:
==> v1/DaemonSet
NAME          DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE
chaos-daemon  6        6        6      6           6          <none>         3m34s

==> v1/Deployment
NAME                      READY  UP-TO-DATE  AVAILABLE  AGE
chaos-controller-manager  0/1    1           0          3m33s

==> v1/Pod(related)
NAME                                       READY  STATUS            RESTARTS  AGE
chaos-controller-manager-75ff888c45-h9mzq  0/1    CrashLoopBackOff  1         3m31s
chaos-daemon-2tc5d                         1/1    Running           0         3m31s
chaos-daemon-6rvzf                         1/1    Running           0         3m33s
chaos-daemon-dxspp                         1/1    Running           0         3m32s
chaos-daemon-hlxch                         1/1    Running           0         3m32s
chaos-daemon-mgqrd                         1/1    Running           0         3m31s
chaos-daemon-qst4j                         1/1    Running           0         3m31s

==> v1/Service
NAME                           TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)  AGE
chaos-mesh-controller-manager  ClusterIP  10.106.44.160  <none>       443/TCP  3m34s

==> v1/ServiceAccount
NAME                      SECRETS  AGE
chaos-controller-manager  1        3m35s

==> v1beta1/ClusterRole
NAME                                 AGE
chaos-mesh:chaos-controller-manager  3m34s

==> v1beta1/ClusterRoleBinding
NAME                                 AGE
chaos-mesh:chaos-controller-manager  3m34s


NOTES:
1. Make sure chaos-mesh components are running
   kubectl get pods --namespace chaos-testing -l app.kubernetes.io/instance=chaos-mesh

More Information

$ kubectl logs po/chaos-controller-manager-75ff888c45-h9mzq -n chaos-testing

Controller manager Version: version.Info{GitVersion:"v0.0.0-master+$Format:%h$", GitCommit:"21cc78511ff065be438d40df5462ef3a8b5448b3", GitTreeState:"clean", BuildDate:"2020-02-10T13:44:53Z", GoVersion:"go1.13", Compiler:"gc", Platform:"linux/amd64"}
2020-02-11T00:04:51.107Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2020-02-11T00:04:51.108Z	INFO	setup	setting up webhook server
2020-02-11T00:04:51.109Z	INFO	inject-webhook	Inferred ConfigMap	{"namespace": "chaos-testing", "filepath": "/var/run/secrets/kubernetes.io/serviceaccount/namespace"}
2020-02-11T00:04:51.109Z	INFO	inject-webhook	Creating Kubernetes client from in-cluster discovery
2020-02-11T00:04:51.113Z	INFO	inject-webhook	Created ConfigMap watcher	{"apiserver": "https://10.96.0.1:443", "namespaces": "chaos-testing", "watchlabels": {"app.kubernetes.io/component":"webhook"}}
2020-02-11T00:04:51.113Z	INFO	controller-runtime.webhook	registering webhook	{"path": "/inject-v1-pod"}
2020-02-11T00:04:51.113Z	INFO	setup	Starting manager
2020-02-11T00:04:51.114Z	INFO	controller-runtime.controller	Starting EventSource	{"controller": "iochaos", "source": "kind source: /, Kind="}
2020-02-11T00:04:51.116Z	INFO	controller-runtime.controller	Starting Controller	{"controller": "iochaos"}
2020-02-11T00:04:51.116Z	INFO	setup	Launching watcher for ConfigMaps
2020-02-11T00:04:51.117Z	INFO	inject-webhook	Watching for ConfigMaps for changes	{"namespace": "chaos-testing", "labels": {"app.kubernetes.io/component":"webhook"}}
2020-02-11T00:04:51.118Z	INFO	controller-runtime.controller	Starting EventSource	{"controller": "networkchaos", "source": "kind source: /, Kind="}
2020-02-11T00:04:51.118Z	INFO	controller-runtime.controller	Starting Controller	{"controller": "networkchaos"}
2020-02-11T00:04:51.118Z	INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
2020-02-11T00:04:51.119Z	INFO	controller-runtime.webhook.webhooks	starting webhook server
2020-02-11T00:04:51.119Z	DEBUG	controller-runtime.manager	non-leader-election runnable finished	{"runnable type": "*webhook.Server"}
2020-02-11T00:04:51.119Z	ERROR	setup	problem running manager	{"error": "tls: failed to find any PEM data in certificate input"}
github.com/go-logr/zapr.(*zapLogger).Error
	/home/jenkins/agent/workspace/build_chaos_mesh_master/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
main.main
	/home/jenkins/agent/workspace/build_chaos_mesh_master/go/src/github.com/pingcap/chaos-mesh/cmd/controller-manager/main.go:151
runtime.main
	/usr/local/go/src/runtime/proc.go:203