Add support for serviceAccountName on deploy

This allows setting the service account for the resulting knative
service, which must pre-exist in the namespace to let the deployment
succeed.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>

pkg/functions/function.go

@@ -146,6 +146,12 @@ type DeploySpec struct {
 
 	// Health endpoints specified by the language pack
 	HealthEndpoints HealthEndpoints `yaml:"healthEndpoints,omitempty"`
+
+	// ServiceAccountName is the name of the service account used for the
+	// function pod. The service account must exist in the namespace to
+	// succeed.
+	// More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
+	ServiceAccountName string `yaml:"serviceAccountName,omitempty"`
 }
 
 // HealthEndpoints specify the liveness and readiness endpoints for a Runtime

pkg/knative/deployer.go

@@ -370,7 +370,8 @@ func generateNewService(f fn.Function, decorator DeployDecorator) (*v1.Service,
 							Containers: []corev1.Container{
 								container,
 							},
-							Volumes: newVolumes,
+							ServiceAccountName: f.Deploy.ServiceAccountName,
+							Volumes:            newVolumes,
 						},
 					},
 				},

schema/func_yaml-schema.json

@@ -86,6 +86,10 @@
 					"$schema": "http://json-schema.org/draft-04/schema#",
 					"$ref": "#/definitions/HealthEndpoints",
 					"description": "Health endpoints specified by the language pack"
+				},
+				"serviceAccountName": {
+					"type": "string",
+					"description": "ServiceAccountName is the name of the service account used for the\nfunction pod. The service account must exist in the namespace to\nsucceed.\nMore info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/"
 				}
 			},
 			"additionalProperties": false,