Closed msfussell closed 9 months ago
Currently there is no way to set the config annotation, similar to having no way to set resources, only the default config can be used. The default config, does not seem to be set, we can add a fix for setting the default config.
If the appconfig
Dapr configuration is not found in default
namespace for some reason, the dapr.io/config
parameter will not be set and skipped emitting a warning:
⚠ Dapr configuration "appconfig" not found in namespace "default". Skipping annotation "dapr.io/config"
If the annotation is not skipped, the application deployment will go into crashloop backoff since the config is not there.
I have made the changes locally and tested ....
closed by #1352
Expected Behavior
Cannot get Zipkin to show traces from the mult-app run on K8s deployment. The deployment is missing the configuration annotations. This dapr.io/config | Tells Dapr which Configuration resource to use From here https://docs.dapr.io/reference/arguments-annotations-overview/
Actual Behavior
The multi-app run K8s template https://v1-12.docs.dapr.io/developing-applications/local-development/multi-app-dapr-run/multi-app-template/ does not have this property that can be set in the template. These are the annotations that you see for the deployed applications. Note there is not config annotation.
Steps to Reproduce the Problem
kubectl port-forward svc/zipkin 19411:9411
Release Note
RELEASE NOTE: UPDATE Cannot set the Configuration for an application in Kubernetes Multi-app run