operator-only-functionality.asciidoc 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051
  1. [role="xpack"]
  2. [[operator-only-functionality]]
  3. === Operator-only functionality
  4. NOTE: {cloud-only}
  5. Operator privileges provide protection for APIs and dynamic cluster settings.
  6. Any API or cluster setting that is protected by operator privileges is known as
  7. _operator-only functionality_. When the operator privileges feature is enabled,
  8. operator-only APIs can be executed only by operator users. Likewise,
  9. operator-only settings can be updated only by operator users. The list of
  10. operator-only APIs and dynamic cluster settings are pre-determined in the
  11. codebase. The list may evolve in future releases but it is otherwise fixed in a
  12. given {es} version.
  13. [[operator-only-apis]]
  14. ==== Operator-only APIs
  15. * <<voting-config-exclusions>>
  16. * <<delete-license>>
  17. * <<update-license>>
  18. * <<autoscaling-put-autoscaling-policy>>
  19. * <<autoscaling-delete-autoscaling-policy>>
  20. * <<repo-analysis-api>>
  21. * <<update-desired-nodes>>
  22. * <<get-desired-nodes>>
  23. * <<delete-desired-nodes>>
  24. * <<get-desired-balance>>
  25. * <<delete-desired-balance>>
  26. [[operator-only-dynamic-cluster-settings]]
  27. ==== Operator-only dynamic cluster settings
  28. * All <<ip-filtering,IP filtering>> settings
  29. * The following dynamic <<ml-settings,machine learning settings>>:
  30. - `xpack.ml.node_concurrent_job_allocations`
  31. - `xpack.ml.max_machine_memory_percent`
  32. - `xpack.ml.use_auto_machine_memory_percent`
  33. - `xpack.ml.max_lazy_ml_nodes`
  34. - `xpack.ml.process_connect_timeout`
  35. - `xpack.ml.nightly_maintenance_requests_per_second`
  36. - `xpack.ml.max_ml_node_size`
  37. - `xpack.ml.enable_config_migration`
  38. - `xpack.ml.persist_results_max_retries`
  39. * The <<cluster-routing-disk-threshold,`cluster.routing.allocation.disk.threshold_enabled` setting>>
  40. * The following <<recovery-settings-for-managed-services,recovery settings for managed services>>:
  41. - `node.bandwidth.recovery.operator.factor`
  42. - `node.bandwidth.recovery.operator.factor.read`
  43. - `node.bandwidth.recovery.operator.factor.write`
  44. - `node.bandwidth.recovery.operator.factor.max_overcommit`