Namespace environment variable not set

[helmerm]

Expected Behavior

Namespace environment variable set on daprd process.

Actual Behavior

Namespace variable not set (verified with ProcessExplorer). DAPR_* variables are set.

Steps to Reproduce the Problem

CLI version: 1.4.0 Runtime version: 1.3.0 Man.Dapr.Sidekick 1.1.0 Windows 10

• Create component config which points to non-existing IP (see below)
• Set Namespace in json config to
  • only components from configured namespace should be loaded
• daprd will try to load component configuration and show connection error despite namespace in sidecar config
  • process component mqtt-pubsub error: init timeout for component mqtt-pubsub exceeded after 5s"

pubsub.yml

apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: mqtt-pubsub namespace: remote spec: type: pubsub.mqtt version: v1 metadata:

• name: url value: "mqtt://192.168.137.1:1883"

appsettings.json "DaprSidekick": { "Sidecar": { "Namespace": "local" } }

Release Note

RELEASE NOTE: FIX Missing Namespace environment variable.

[badgeratu]

This is an interesting one - I think we've not come across it because we use mTLS encryption and when that is enabled in Sidekick (i.e. mTLS: "true" in appsettings.json) the NAMESPACE environment variable is set with either a default value of default or the value defined through configuration. You can see the predicate check here. We'll take a look shortly and see how best to fix it, shouldn't take too long.

And thanks for your interest in Sidekick!

[helmerm]

Thank you!

[badgeratu]

Now available in Release v1.2