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 noticed that, with the manifests (or the Helm template) in this repository, the pods for the Portainer server mount a service account with cluster-admin access. However, if I understand correctly, all interactions that Portainer has with Kubernetes are done through the agent, not directly by the server. Is there a reason why the server's pods also need cluster admin access to run?
The text was updated successfully, but these errors were encountered:
Don't need an agent to manage the cluster where Portainer Server is running. Only need to deploy agents to clusters other clusters that you would need to manage.
Hello,
I noticed that, with the manifests (or the Helm template) in this repository, the pods for the Portainer server mount a service account with cluster-admin access. However, if I understand correctly, all interactions that Portainer has with Kubernetes are done through the agent, not directly by the server. Is there a reason why the server's pods also need cluster admin access to run?
The text was updated successfully, but these errors were encountered: