Opensearch-security POD cannot be schedule to specific nodepool

OpenSearch
1

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser): Opensearch and Dashboard version is 3.0.0. Opensearch-controller is 2.7.0

Describe the issue: Opensearch-security POD definition does not support any option to specify a node pool (nodeSelector, nodeAffinity or taints/tolerations). In my values-files I can indicate to the manager, nodes, bootstrap and dashboard PODs the nodepool I want to deploy to, but it seems this options is not available for the opsearch-security POD.

I ran kubectl explain and cannot find it anywhere under opensearchcluster.spec.security.

Is there a way to actually do it at deployment time ?

I’ve been following the user guide for my deployment.

Configuration:

Relevant Logs or Screenshots:

image
image451×268 3.33 KB

2

@GTGabaaron You can use the following configuration:

security:
  config:
    updateJob:
      nodeSelector:
        dedicated: opensearch
      tolerations:
        - key: "dedicated"
          operator: "Equal"
          value: "opensearch"
          effect: "NoSchedule"

However this would need to be used with opensearch-operator-3.0.0 or later (or build from source), as the current image (alpha) doesnt seem to be updated to action this configuration.

Hope this helps