You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rlog.Error(err, "unable to get the specified", "service account", types.NamespacedName{Name: instance.Spec.ServiceAccountRef.Name, Namespace: instance.GetNamespace()})
138
-
return&rest.Config{}, err
145
+
rlog.Error(err, "unable to retrieve secrets", "in namespace", instance.GetNamespace())
146
+
returnnil, err
147
+
}
148
+
for_, secret:=rangesecretList.Items {
149
+
ifsaname, ok:=secret.Annotations["kubernetes.io/service-account.name"]; ok {
rlog.Error(err, "(ignoring) unable to get ", "ref secret", types.NamespacedName{Name: secretRef.Name, Namespace: instance.GetNamespace()})
146
-
continue
164
+
rlog.Error(err, "unable to get the specified", "service account", types.NamespacedName{Name: instance.Spec.ServiceAccountRef.Name, Namespace: instance.GetNamespace()})
Copy file name to clipboardExpand all lines: readme.md
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -385,6 +385,18 @@ The `deployer` service accounts from all namespaces are selected as target of th
385
385
386
386
The patch enforcement enacted by the patch controller is executed with a client which uses the service account referenced by the `serviceAccountRef` field. So before a patch object can actually work an administrator must have granted the needed permissions to a service account in the same namespace. The `serviceAccountRef` will default to the `default` service account if not specified.
387
387
388
+
_Note:_ with kubernetes 1.24, service account token secrets are not created automatically anymore (see also [here](https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets)). The path-operator relies on these secrets. So you have to create the secret for the service account referenced in the `serviceAccountRef`. Here is an example of how to create a service account token secret for the `default` service account:
389
+
390
+
```yaml
391
+
apiVersion: v1
392
+
kind: Secret
393
+
metadata:
394
+
name: default-service-account-secret
395
+
annotations:
396
+
kubernetes.io/service-account.name: "default"
397
+
type: kubernetes.io/service-account-token
398
+
```
399
+
388
400
### Patch Controller Performance Considerations
389
401
390
402
The patch controller will create a controller-manager and per `Patch` object and a reconciler for each of the `PatchSpec` defined in the array on patches in the `Patch` object.
0 commit comments