only copy over the queue information to the worker static config

[thisisibrahimd]

No description provided.

[L1ghtman2k]

LGTM

[thisisibrahimd]

I am getting errors when deploying to non default namespaces. The daemonsets are only getting deployed to default namespace.

[L1ghtman2k]

I am getting errors when deploying to non default namespaces. The daemonsets are only getting deployed to default namespace.

This might not be related to this issue? I don't think worker CFG decides where workers get deployed. I think this is just how app behaved all along, and we could track this as a separate issue

[L1ghtman2k]

Hm, interesting app has access to deploy to other namespaces, Perhaps we can downgrade perms from cluster role, to role for this one

[thisisibrahimd]

It might not be related to this issue, but an interesting issue for sure. I am assuming it was never deployed in a non default namespace for lockdown because nsq would not work at all.
Though, the cfg from the master cfg.platform.namespace is used to decide namespace meta object for daemonset spec and pod spec.

Will decrease the perms for cluster role then.

[L1ghtman2k]

I think we can do following:

• Allow overwriting namespace field for workers, but by default deploy it in the same namespace as mater

[L1ghtman2k]

#312

[thisisibrahimd]

good to go.