Which command would patch a deployment config to set the service account name to myserviceaccount?

Which command would patch a deployment config to set the service account name to myserviceaccount?

• A. oc patch dc/demo-app --patch '{"spec":{"template":{"spec":{"serviceAccountName": "myserviceaccount"}}}}'
• B. oc patch dc/demo-app --patch '{"spec":{"template":{"serviceAccountName": "other"}}}'
• C. oc patch dc/demo-app --patch '{"spec":{"template":{"serviceAccount": "myserviceaccount"}}}'
• D. oc patch dc/demo-app --patch '{"template":{"spec":{"serviceAccountName": "myserviceaccount"}}}}'

Answer: (A)

The key idea is updating the service account for pods created by the DeploymentConfig, which lives in the pod template inside the DeploymentConfig. To change it, you patch the field at spec.template.spec.serviceAccountName with the desired value. The correct patch does exactly that: it targets spec.template.spec.serviceAccountName and sets it to "myserviceaccount". This aligns with where OpenShift stores the pod’s service account in a DeploymentConfig. The other options fail because they either place the field in the wrong level (for example, setting serviceAccountName at the template level rather than inside template.spec), use a different field name (serviceAccountName vs serviceAccount), or have invalid JSON structure (such as an extra brace or incorrect nesting).

The key idea is updating the service account for pods created by the DeploymentConfig, which lives in the pod template inside the DeploymentConfig. To change it, you patch the field at spec.template.spec.serviceAccountName with the desired value.

The correct patch does exactly that: it targets spec.template.spec.serviceAccountName and sets it to "myserviceaccount". This aligns with where OpenShift stores the pod’s service account in a DeploymentConfig.

The other options fail because they either place the field in the wrong level (for example, setting serviceAccountName at the template level rather than inside template.spec), use a different field name (serviceAccountName vs serviceAccount), or have invalid JSON structure (such as an extra brace or incorrect nesting).