We are using the Atlas Kubernetes Operator (v2.8.2) to manage Atlas deployments and use dedicated Search Nodes.

We would like to use the Atlas Admin API to scale up larger search nodes then scale back down after our daily processing window, but the k8s operator doesn't allow this currently. After I send an API request to scale search nodes the k8s operator waits for the search nodes to be ready and then reverts to the values set in the AtlasDeployment.

Similar to compute/disk autoscaling an "enabled" flag for the search node reconciliation would give more flexibility to leverage the Admin API for custom search node scaling.