fix typo and other issues

[DanielZhangQD]

What problem does this PR solve?

Fix a typo in tiflash config and fixes #2218, #2219

What is changed and how does it work?

Check List

Tests

• Manual test (add detailed scripts or steps below)
  • Deploy TidbCluster with below CR and enable-placement-rules will be enabled automatically for PD, all the components can be started successfully.

apiVersion: pingcap.com/v1alpha1
kind: TidbCluster
metadata:
  name: test30
  namespace: test30
spec:
  configUpdateStrategy: RollingUpdate
  enablePVReclaim: false
  imagePullPolicy: IfNotPresent
  pd:
    affinity: {}
    baseImage: pingcap/pd
    config:
      log:
        level: info
      replication:
        location-labels:
        - region
        - zone
        - rack
        - host
        max-replicas: 3
    image: pingcap/pd:nightly
    imagePullPolicy: IfNotPresent
    maxFailoverCount: 3
    replicas: 1
    requests:
      storage: 1Gi
    storageClassName: local-storage
  pvReclaimPolicy: Delete
  schedulerName: tidb-scheduler
  services:
  - name: pd
    type: ClusterIP
  tidb:
    affinity: {}
    baseImage: pingcap/tidb
    config:
      log:
        file:
          max-backups: 3
        level: info
    image: pingcap/tidb:nightly
    imagePullPolicy: IfNotPresent
    maxFailoverCount: 3
    replicas: 1
    separateSlowLog: true
    slowLogTailer:
      image: busybox:1.26.2
      imagePullPolicy: IfNotPresent
      limits:
        cpu: 100m
        memory: 50Mi
      requests:
        cpu: 20m
        memory: 5Mi
  tiflash:
    baseImage: pingcap/tiflash
    config:
      config:
        logger:
          errorlog: /data0/logs/error.log
          count: 5
    replicas: 1
    storageClaims:
    - resources:
        requests:
          storage: 10Gi
      storageClassName: local-storage
  tikv:
    affinity: {}
    baseImage: pingcap/tikv
    config:
      log-level: info
    image: pingcap/tikv:nightly
    imagePullPolicy: IfNotPresent
    maxFailoverCount: 3
    replicas: 1
    requests:
      storage: 10Gi
    storageClassName: local-storage
  tlsCluster: {}
  version: v3.1.0-rc

Code changes

• Has Go code change

Related changes

• Need to cherry-pick to the release branch

Does this PR introduce a user-facing change?:

NONE

[DanielZhangQD]

/run-e2e-tests

[weekface]

LGTM

[DanielZhangQD]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

/run-all-tests

[sre-bot]

@DanielZhangQD merge failed.

[DanielZhangQD]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

/run-all-tests

[sre-bot]

@DanielZhangQD merge failed.

[DanielZhangQD]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

@DanielZhangQD merge failed.

[DanielZhangQD]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

@DanielZhangQD merge failed.

[DanielZhangQD]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

cherry pick to release-1.1 in PR #2280