k8s cluster worker pod is using wrong config

I have simple 2 replica cluster, when I start up the cluster it is having broken config file in it

101 is searchd pid

# ps -fp 101
UID          PID    PPID  C STIME TTY          TIME CMD
root         101      94  0 19:30 ?        00:00:00 searchd -c /etc/manticoresearch/manticore.conf --nodetach
# cat /etc/manticoresearch/manticore.conf
#!/bin/sh
sed 's/$hostname/'$(hostname -f)'/' $CONFIGMAP_PATH | sed 's/\.svc\.cluster\.local//'

# cat $CONFIGMAP_PATH
searchd
{
  listen = /var/run/mysqld/mysqld.sock:mysql41
  listen = 9306:mysql41
  listen = 9308:http
  listen = 9301:mysql_vip
  listen = $hostname:9312
  listen = $hostname:9315-9415:replication
  node_address = $hostname
  binlog_path = /var/lib/manticore
  query_log = /dev/stdout
  query_log_format = sphinxql
  pid_file = /var/run/manticore/searchd.pid
  data_dir = /var/lib/manticore
  shutdown_timeout = 25s
  auto_optimize = 0
}
# echo $CONFIGMAP_PATH
/mnt/manticore.conf

it seems sed failed to fix the config file content, on top of it searchd is not using the $CONFIGMAP_PATH file, using default conf file

I discovered when I run create table query.
[CREATE TABLE requires data_dir to be set in the config file](https://forum.manticoresearch.com/t/create-table-requires-data-dir-to-be-set-in-the-config-file/735)

This happens with all 7.xx chart versions

created an issue: cluster worker pod is using wrong config · Issue #123 · manticoresoftware/manticoresearch-helm · GitHub

Any help

Discussed in TG Telegram: Contact @manticoresearch_en