---------------------- To set a

serviceAccountName

for a pod created as a container type, you can specify it in the

spec.podSpec

of your configuration. This should be a normal Kubernetes Pod manifest. Here is an example of how you can set it:

yaml
spec:
  podSpec:
    serviceAccountName: <your-service-account-name>

Please replace

<your-service-account-name>

with the name of your service account. You can find more details about the

spec.podSpec

in the official Garden documentation (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

@microscopic-river-74022 can i affect the kubernetes manifest while using container type, not kubernetes type?

---------------------- The

container

action type in Garden is a simplified abstraction and it automatically generates Kubernetes manifests for you. However, it does not provide direct access to modify the Kubernetes manifests. If you need to use advanced features of the underlying platform or modify the Kubernetes manifests directly, you may need to use more platform-specific action types like

kubernetes

or

helm

. For example, with the

kubernetes

deploy type, you can use manifest yaml files and set specific configurations like

imagePullPolicy

as mentioned in the Discord support thread (). If you need to use the

container

type and also need to modify the Kubernetes manifests, you might want to follow the progress of the

kubernetes-container

action type that is being planned as mentioned in the Github Issue (). This new action type would allow extending the config of the

container

type with Kubernetes specific fields. For more information on the

container

action type, you can refer to the official Garden documentation (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------