You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For every dapr sidecar that gets created, a cluster ip service gets created for the sidecar. This is represented in k8s with the <appid>-dapr nomenclature.
However, when deploying nginx via a daemonset, this service is not created automatically, requiring a manual process. It'd be ideal if Dapr could handle this service creation during deployment.
This can be easily reproduced by following the DaemonSet deployment process here but adding Dapr annotations to the DameonSet yaml file.
Release Note
RELEASE NOTE: ADDED support to automated sidecar service creation for ingress controller via DaemonSet
The text was updated successfully, but these errors were encountered:
In what area(s)?
/area operator
Describe the feature
For every dapr sidecar that gets created, a cluster ip service gets created for the sidecar. This is represented in k8s with the
<appid>-dapr
nomenclature.However, when deploying
nginx
via a daemonset, this service is not created automatically, requiring a manual process. It'd be ideal if Dapr could handle this service creation during deployment.This can be easily reproduced by following the DaemonSet deployment process here but adding Dapr annotations to the DameonSet yaml file.
Release Note
RELEASE NOTE: ADDED support to automated sidecar service creation for ingress controller via DaemonSet
The text was updated successfully, but these errors were encountered: