Remove resourceNames in integration secrets
* Solves #1524 * We remove resourceName due to the following: Note: You cannot restrict create or deletecollection requests by resourceName. For create, this limitation is because the object name is not known at authorization time. * Fix typo in azure-registry cronjob Signed-off-by: Edvin Norling <edvin.norling@xenit.se>
This commit is contained in:
@@ -110,8 +110,8 @@ rules:
|
||||
- update
|
||||
- patch
|
||||
# Lock this down to the specific Secret name (Optional)
|
||||
resourceNames:
|
||||
- $(KUBE_SECRET) # templated from kustomize vars referencing ConfigMap, also see kustomizeconfig.yaml
|
||||
#resourceNames:
|
||||
# - $(KUBE_SECRET) # templated from kustomize vars referencing ConfigMap, also see kustomizeconfig.yaml
|
||||
---
|
||||
kind: RoleBinding
|
||||
apiVersion: rbac.authorization.k8s.io/v1
|
||||
|
||||
Reference in New Issue
Block a user