Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dapr-sidecar-injector patch the injector to the application pods #7809

Open
kiranagalpady83 opened this issue Jun 12, 2024 · 2 comments
Open

Comments

@kiranagalpady83
Copy link

Note: If you have a general support question and are looking for a quicker response, please checkout our discord channel for answers from the community:
https://aka.ms/dapr-discord

In what area(s)?

/area runtime

Ask your question here:

Hello, Do we need following ServiceAccount in kuberenetes cluster to function the Dapr-sidecar-injector patch the injector to the application pods?
ServiceAccount list:

system:kube-controller-manager                                                                                                                                                                                                                       kube-system:replicaset-controller
kube-system:deployment-controller
kube-system:cronjob-controller
kube-system:job-controller
kube-system:statefulset-controller
kube-system:daemon-set-controller
tekton-pipelines:tekton-pipelines-controller
@yaron2
Copy link
Member

yaron2 commented Jun 12, 2024

Generally yes, but you can tell Dapr which service accounts to use. What is the service account in your cluster that is used for deploying your pods?

@kiranagalpady83
Copy link
Author

kiranagalpady83 commented Jun 14, 2024

logs.txt
we use the serviceaccount where helm chart deployment file defined server accounts for dapr deployment and for application deployment we use default serviceaccounts. We don't have access to kube-system namespace. Dapr sidecar injector is not patching injector to the application pods. please find the attached logs.
logs.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants