operator-only-snapshot-and-restore.asciidoc 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. [role="xpack"]
  2. [testenv="enterprise"]
  3. [[operator-only-snapshot-and-restore]]
  4. === Operator privileges for snapshot and restore
  5. NOTE: {cloud-only}
  6. Invoking <<operator-only-apis,operator-only APIs>> or updating
  7. <<operator-only-dynamic-cluster-settings,operator-only dynamic cluster settings>>
  8. typically results in changes in the cluster state. The cluster state can be
  9. included in a cluster <<snapshot-restore,snapshot>>. Snapshots are a great way
  10. to preserve the data of a cluster, which can later be restored to bootstrap a
  11. new cluster, perform migration, or disaster recovery, for example. In a
  12. traditional self-managed environment, the intention is for the restore process
  13. to copy the entire cluster state over when requested. However, in a more
  14. managed environment, such as {ess-trial}[{ess}], data that is associated with
  15. <<operator-only-functionality,operator-only functionality>> is explicitly
  16. managed by the infrastructure code.
  17. Restoring snapshot data associated with
  18. operator-only functionality could be problematic
  19. because:
  20. 1. A snapshot could contain incorrect values for operator-only functionalities.
  21. For example, the snapshot could have been taken in a different cluster where
  22. requirements are different or the operator privileges feature is not enabled.
  23. Restoring data associated with operator-only functionality breaks the guarantee
  24. of operator privileges.
  25. 2. Even when the infrastructure code can correct the values immediately after
  26. a restore, there will always be a short period of time when the cluster could be
  27. in an inconsistent state.
  28. 3. The infrastructure code prefers to configure operator-only functionality from
  29. a single place, that is to say, through API calls.
  30. Therefore,
  31. <<configure-operator-privileges,*when the operator privileges feature is enabled*>>,
  32. snapshot data that is associated with any operator-only functionality is *not*
  33. restored.
  34. NOTE: That information is still included when taking a snapshot so that all data
  35. is always preserved.