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
I have Dapr installed in my Kubernetes cluster using the Helm Chart version 1.10.4. It is working perfectly, and I have a couple of applications listed on the dashboard. It should be noted that these applications are ReplicaSets with the Dapr sidecar running in the same pod, injected by the sidecar-injector using Dapr podAnnotations.
The problem:
I am also installing Keycloak using a Helm Chart. However, instead of being a ReplicaSet, Keycloak is implemented as a StatefulSet. I was able to add the Dapr annotations to the Keycloak pods, and the sidecar was successfully injected into the pods. In fact, Dapr can interact with Keycloak without any issues. The only problem is that Keycloak does not show up in the list of applications on the Dapr Dashboard.
I understand that the Dapr Dashboard might not fully support StatefulSets yet, but it would be great if this feature could be added in future releases to provide a more comprehensive view of all Dapr-enabled applications in a cluster, regardless of whether they are ReplicaSets or StatefulSets.
Thank you.
The text was updated successfully, but these errors were encountered:
Changes made in instances.go
* Get kubernetes instances including StatefulSets
* Update GetMetadata method
* Update GetDeploymentConfiguration method
* Update Logstream to read container logs from StatefulSets
Changes made in helmchart:
* include statefulsets as allowed resource for Role/ClusterRole CDR
* Update dashboard.yaml to allow statefulsets in Role/ClusterRole CDR
Signed-off-by: fabrizziocht <[email protected]>
Changes made in instances.go
* Get kubernetes instances including StatefulSets
* Update GetMetadata method
* Update GetDeploymentConfiguration method
* Update Logstream to read container logs from StatefulSets
Changes made in helmchart:
* include statefulsets as allowed resource for Role/ClusterRole CDR
* Update dashboard.yaml to allow statefulsets in Role/ClusterRole CDR
Signed-off-by: fabrizziocht <[email protected]>
Co-authored-by: Yaron Schneider <[email protected]>
I have Dapr installed in my Kubernetes cluster using the Helm Chart version 1.10.4. It is working perfectly, and I have a couple of applications listed on the dashboard. It should be noted that these applications are ReplicaSets with the Dapr sidecar running in the same pod, injected by the sidecar-injector using Dapr podAnnotations.
The problem:
I am also installing Keycloak using a Helm Chart. However, instead of being a ReplicaSet, Keycloak is implemented as a StatefulSet. I was able to add the Dapr annotations to the Keycloak pods, and the sidecar was successfully injected into the pods. In fact, Dapr can interact with Keycloak without any issues. The only problem is that Keycloak does not show up in the list of applications on the Dapr Dashboard.
I understand that the Dapr Dashboard might not fully support StatefulSets yet, but it would be great if this feature could be added in future releases to provide a more comprehensive view of all Dapr-enabled applications in a cluster, regardless of whether they are ReplicaSets or StatefulSets.
Thank you.
The text was updated successfully, but these errors were encountered: