Advanced visibility with Postgres configuration issue

Community Support Server Deployment
1

Hi, Community!

I faced with problem that service pods (frontend, history, matching, worker) failed to start with message

config validation error: persistence config: advanced visibility datastore "visibility": must provide config for "elasticsearch"

So as already mentioned, my goal is to run advanced visibility feature using Postgres.

In config validation code here actually only validation for ES, so I think it fails here.

I use v1.20.1 version. Already saw this post.

Before deployment I run migration - it completed without any problem

SQL_DATABASE=temporal $TEMPORAL_HOME/temporal-sql-tool setup-schema -v 0.0
SQL_DATABASE=temporal $TEMPORAL_HOME/temporal-sql-tool update -schema-dir $TEMPORAL_HOME/schema/postgresql/v12/temporal/versioned

SQL_DATABASE=temporal_visibility $TEMPORAL_HOME/temporal-sql-tool setup-schema -v 0.0
SQL_DATABASE=temporal_visibility $TEMPORAL_HOME/temporal-sql-tool update -schema-dir $TEMPORAL_HOME/schema/postgresql/v12/visibility/versioned

My persistency config is:

persistence:
  defaultStore: default
  advancedVisibilityStore: visibility
  numHistoryShards: 512
  datastores:
    default:
      sql:
        pluginName: "postgres12"
        driverName: "postgres12"
        databaseName: "temporal"
        connectAddr: "host.minikube.internal:5432"
        connectProtocol: "tcp"
        user: root
        password: "{{ .Env.TEMPORAL_STORE_PASSWORD }}"
        maxConnLifetime: 1h
        maxConns: 20
        secretName: ""
    visibility:
      sql:
        pluginName: "postgres12"
        driverName: "postgres12"
        databaseName: "temporal_visibility"
        connectAddr: "host.minikube.internal:5432"
        connectProtocol: "tcp"
        user: "root"
        password: "{{ .Env.TEMPORAL_VISIBILITY_STORE_PASSWORD }}"
        maxConnLifetime: 1h
        maxConns: 20
        secretName: ""

What am I doing wrong?

Thanks in advance.