while setting up crdb in our k8s cluster, I've noticed that setting up a policy for backups in the cluster is not a setting I can do.
Is that by design?
Would you consider adding a setting to the operator, to enforce a standard backup policy for all created / managed crdb clusters in the cluster?
Ideally this would be overridable from the custom resource that defines the actual crdb, but that way the operator could ensure to not only create the database, but also initialize the backups, making it very hard to miss initializing them.
What do you think? Am I missing something that makes this already possible?
Hi there,
while setting up crdb in our k8s cluster, I've noticed that setting up a policy for backups in the cluster is not a setting I can do.
Is that by design?
Would you consider adding a setting to the operator, to enforce a standard backup policy for all created / managed crdb clusters in the cluster?
Ideally this would be overridable from the custom resource that defines the actual crdb, but that way the operator could ensure to not only create the database, but also initialize the backups, making it very hard to miss initializing them.
What do you think? Am I missing something that makes this already possible?