Enable Namespace Not Active Auto Forwarding

Community Support Server Deployment
1

Hi,
how do I configure namespaces for system.enableNamespaceNotActiveAutoForwarding? If I don’t configure any specific namespaces, does it mean the config is valid for all namespaces or for zero namespaces? I can’t make it work.

I’ve tried:

system.enableNamespaceNotActiveAutoForwarding:
  - value: true
    constraints:
      namespace: "namespace1"

Also

system.enableNamespaceNotActiveAutoForwarding:
  - value: true
    constraints: {}

and

system.enableNamespaceNotActiveAutoForwarding:
  - value: true

But it seems that the config is simply ignored as if I try to start a workflow with tctl workflow start I get error:

Error Details: Namespace: namespace1 is active in cluster: cluster1, while current cluster cluster2 is a standby cluster.

Or am I misunderstanding something?

2

Any update on this ?

3

on the static config, you need to enable the below config. default policy is noop. you can choose between all-apis-forwarding or selected-apis-forwarding.
dcRedirectionPolicy:
policy: “all-apis-forwarding”

1 Like