How to Properly Use The Roles in values.yaml?

Elastic Stack Elasticsearch
1

Hi Team,

I've been having a problem correcting the deprecation warnings related to node.roles:

"message": "legacy role settings [node.data, node.remote_cluster_client, node.ingest, node.master, node.ml] are deprecated, use [node.roles=[transform, data_frozen, master, data, data_content, data_hot, data_warm, data_cold]]"

This is so far the values I am using for our ES multi-cluster:

nodeGroup: "master"
replicas: 3

roles:
  master: "true"
  ingest: "false"
  data: "true"
  remote_cluster_client: "false"
  ml: "false"

esConfig:
  elasticsearch.yml: |
    xpack.security.enabled: false

resources:
  requests:
    cpu: "100m"
    memory: "4Gi"

  limits:
    cpu: "1"
    memory: "4Gi"

volumeClaimTemplate:
  accessModes: [ "ReadWriteOnce" ]
  storageClassName: monitoring
  resources:
    requests:
      storage: 4Gi

We are using the latest chart version 7.16.3. With this, will this new set of values work for the node roles?

nodeGroup: "master"
replicas: 3

roles:
  - master

And no definition for node.roles should be added within the elasticsearch.yml?

Thanks in advance! Apologies, I've been stuck on correcting the deprecation warnings and your response will highly be appreciated!

2

Please check this documentation. they have still define values in old way only. Also, Chart 7.17 is support old way. this will be coming in next release as i can see changes in Main branch which is showing roles in new way.

3

Thanks sagarpatel, yeah, it looks like they still are using the old format. But would you know how to resolve the deprecation warning such as below:

{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,152Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "[node.ml] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.ml", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,177Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "[node.data] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.data", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,241Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "[node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.master", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,246Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "[node.remote_cluster_client] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.remote_cluster_client", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,252Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "[node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.ingest", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2022-03-07T07:56:19,349Z", "level": "CRITICAL", "component": "o.e.d.n.Node", "cluster.name": "elasticsearch", "node.name": "elasticsearch-data-0", "message": "legacy role settings [node.data, node.remote_cluster_client, node.ingest, node.master, node.ml] are deprecated, use [node.roles=[transform, data_frozen, data, data_content, data_hot, data_warm, data_cold, ingest]]", "key": "legacy role settings", "category": "settings" }

These are all node related deprecation warnings.

4

You can use current functionality with deprecation log and to resolved this you need to upgrade version. If you want to test then you can provide roles in new way and tried out but my understanding is, it will not worked. So go with current version as of now and when new version release upgrade it (chart).

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.