binlog: add tls in pump and drainer

[shuijing198799]

What problem does this PR solve?

add tls for drainer and pump component in tidb cluster， make pump and drainer can be interconnected with other components in k8s with tls.

What is changed and how does it work?

add a script to generate the secret of pump and drainer which approved by k8s, add tls trigger in drainer, and attach secret volume to pump and drainer pod.

Check List

Tests

• Unit test
• E2E test
  e2e test is running in local compute however the binlog should compatible with the old and new binlog. It will exist in other PR
  drainer flag compatible with the old version tidb-binlog#908
• Stability test (in testing)
• Manual test (add detailed scripts or steps below)

create the source cluster namespace

$ kubectl create ns $sourceNS

create certification secret for pump

$ ./hack/create-cert.sh --namespace $sourceNS --component pump --cluster $sourceClusterName

deploy a tidbluster with tls and pump

$ helm install pingcap/tidb-cluster  --name $sourceCluster --namespace $sourceNS --set-string binlog.pump.create=true,,enableTLSCluster=true,clusterName=$sourceClusterName --values $value.yaml

create certification secret for drainer

$ ./hack/create-cert.sh --namespace $sourceNS --component drainer --cluster $sourceClusterName

deploy a drainer cluster with tls

helm install pingcap/tidb-drainer  --name $drainerName --namespace $sourceNS --set-string clusterName=$sourceClusterName,enableTLSCluster=true -f $values.yaml

Code changes

• Has Go code change
• Has yaml change

[shuijing198799]

The binlog PR has just been closed and is being manually tested.

[cofyc]

LGTM

[DanielZhangQD]

LGTM

[aylei]

LGTM

[shuijing198799]

/merge

[sre-bot]

/run-all-tests