br: `.spec.pause` is missing from backupschedule manifest after backup is created about tidb-operator HOT 5 OPEN

@hongshaoyang did you set the value of paused (pause: ${var.is_backup_paused}) to true or false? some default values may be absent in the manifest.

from tidb-operator.

@csuzhangxc - it is set to the default, false, that is, scheduled backups are not paused.

some default values may be absent in the manifest.

but that is not expected. this will cause issues with infrastructure-as-code tools like terraform which expect values to not change over time.

from tidb-operator.

specially, for this pause: false, I tested it on Kubernetes server v1.27.3 and client v1.29.0, I can get it back with -o yaml.

Can you try it on other versions of server and client?

from tidb-operator.

Our GKE clusters are standardised to be the same version across. So I cannot try it on other versions.

One observation is that after applying the Kube manifest, I also can view the pause: false field immediately with -o yaml. But after a while (after the backup was created) the .spec.pause field became absent.

from tidb-operator.

but that is not expected. this will cause issues with infrastructure-as-code tools like terraform which expect values to not change over time.

One possible method to resolve it may not set these empty values in IaC tools as K8s/Golang-JSON has the omitempty behavior.

from tidb-operator.