add pod labels to spire server values (#271)

* add pod labels to spire server values

The reason for this change is to be able to integrate spire with Azure
Workload Idenity. To enable this, a label of `azure.workload.identity/use: "true"` needs
to be added to the pods metadata.

https://learn.microsoft.com/en-us/azure/aks/learn/tutorial-kubernetes-workload-identity#deploy-the-workload

Signed-off-by: Rory Houlihan <[email protected]>

* trim whitespace from podLabels
Signed-off-by: Rory Houlihan <[email protected]>

---------

Signed-off-by: Rory Houlihan <[email protected]>
This commit is contained in:
McRors Calhoun
2024-03-01 08:37:38 -08:00
committed by GitHub
parent f512b06419
commit 5849ea2c82
3 changed files with 7 additions and 0 deletions
@@ -95,6 +95,7 @@ In order to run Tornjak with simple HTTP Connection only, make sure you don't cr
| `serviceAccount.annotations` | Annotations to add to the service account | `{}` |
| `serviceAccount.name` | The name of the service account to use. If not set and create is true, a name is generated. | `""` |
| `podAnnotations` | Annotations to add to pods | `{}` |
| `podLabels` | Labels to add to pods | `{}` |
| `podSecurityContext` | Pod security context | `{}` |
| `securityContext` | Security context | `{}` |
| `priorityClassName` | Priority class assigned to statefulset pods. Can be auto set with global.recommendations.priorityClassName. | `""` |