EronWright commented on issue #19771: URL: https://github.com/apache/pulsar/issues/19771#issuecomment-1481641279
@michaeljmarshall sorry for the delayed response. About the function pod's service account, I would like to share my thoughts about that. The pod's KSA can be understood as the 'workload identity' of the pod. It is the identity that the function will have when talking to Pulsar, and to other cloud services too. For example, a "Cloud Storage Sink" connector (which is a type of function) would naturally authenticate to S3 using its workload identity (see [IRSA](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html)). It seems important that the function submitter not be able to escalate their privileges by selecting an arbitrary service account. I feel that the function worker service (e.g. the function mesh) assign a service account. I would hesistate to automatically create service accounts, because of the complexity of setting up the workload identity. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
