Skip to content

br: add a new check for tikv encryption during the volume-snapshot restore #4913

@fengou1

Description

@fengou1

Bug Report

What version of Kubernetes are you using?
[root@kvm-dev kms]# kubectl version Client Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.6-eks-7d68063", GitCommit:"f24e667e49fb137336f7b064dba897beed639bad", GitTreeState:"clean", BuildDate:"2022-02-23T19:32:14Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.16-eks-ffeb93d", GitCommit:"52e500d139bdef42fbc4540c357f0565c7867a81", GitTreeState:"clean", BuildDate:"2022-11-29T18:41:42Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

What version of TiDB Operator are you using?
v1.5.alpha.5

What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
NA

What's the status of the TiDB cluster pods?

What did you do?
volume snapshot restore support

  • both backup and restore with the same encryption
  • backup without encryption and restore has encryption

volume snapshot restore does not support

  • backup has encryption and restore has not

What did you expect to see?
when volume snapshot does not support scenario happened, do not launch the restore to save the resource

What did you see instead?
restore is happened, and finally failure at the very end of restore stage

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions