You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Annotations in global level for OpenSearch-Cluster Helm Chart
What are you proposing?
Currently the cluster.annotations is set only to the OpenSearchCluster manifest, not the all pods created from nodePools. So, proposing to have an annotation input globally and inherit to all, then the child level added should be overridden or append.
What problems are you trying to solve?
The cluster resource creation is done properly with the annotations, but not for the nodePools currently. There are tools in Kubernetes running for inventory purposes and which takes inputs from annotations too. These inventory-based tools are focusing the resources in Kubernetes which consumes the capacity (ex. CPU, Mem, Disk, etc...). Since the nodePool is not having any annotation, it returns null.
It is possible to explicitly mention the annotations in each nodePool component, but this will be duplicate. Since the cluster is used for same purpose, the annotations should be same in all nodePool components.
The text was updated successfully, but these errors were encountered:
Annotations in global level for OpenSearch-Cluster Helm Chart
What are you proposing?
Currently the
cluster.annotations
is set only to theOpenSearchCluster
manifest, not the all pods created fromnodePools
. So, proposing to have an annotation input globally and inherit to all, then the child level added should be overridden or append.What problems are you trying to solve?
The cluster resource creation is done properly with the annotations, but not for the
nodePools
currently. There are tools in Kubernetes running for inventory purposes and which takes inputs from annotations too. These inventory-based tools are focusing the resources in Kubernetes which consumes the capacity (ex.CPU, Mem, Disk, etc...
). Since thenodePool
is not having any annotation, it returns null.It is possible to explicitly mention the annotations in each
nodePool
component, but this will be duplicate. Since the cluster is used for same purpose, the annotations should be same in allnodePool
components.The text was updated successfully, but these errors were encountered: