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:
@@ -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. | `""` |
|
||||
|
||||
@@ -43,6 +43,9 @@ spec:
|
||||
component: server
|
||||
release: {{ .Release.Name }}
|
||||
release-namespace: {{ .Release.Namespace }}
|
||||
{{- with .Values.podLabels }}
|
||||
{{- toYaml . | nindent 8 }}
|
||||
{{- end }}
|
||||
spec:
|
||||
{{- with .Values.imagePullSecrets }}
|
||||
imagePullSecrets:
|
||||
|
||||
@@ -47,6 +47,9 @@ serviceAccount:
|
||||
## @param podAnnotations [object] Annotations to add to pods
|
||||
podAnnotations: {}
|
||||
|
||||
## @param podLabels [object] Labels to add to pods
|
||||
podLabels: {}
|
||||
|
||||
## @param podSecurityContext [object] Pod security context
|
||||
podSecurityContext: {}
|
||||
# fsGroup: 2000
|
||||
|
||||
Reference in New Issue
Block a user