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:
@@ -49,7 +49,7 @@ spec:
|
||||
|
||||
apply-secret() {
|
||||
/kbin/kubectl create secret docker-registry "${1}" \
|
||||
--docker-passwrod="${2}" \
|
||||
--docker-password="${2}" \
|
||||
--docker-username="${3}" \
|
||||
--docker-server="${4}" \
|
||||
--dry-run=client -o=yaml \
|
||||
|
||||
Reference in New Issue
Block a user