Fixing some kustomizeconfig.yaml files.

Since `[email protected]`, `yaml.UnmarshalStric()` is used instead of
`yaml.Unmarshal()` which means that fields in the yamls that doesn't exist
in the golang object will fail to unmarshal instead of being ignored
like they would without the `strict` behavior.

Therefore, those redundant `name` fields where removed.

In addition, I have bumped `[email protected]` --> `[email protected]`
to make sure we get a closer behavior on machines that comes with
`kustomize` pre-installed and those which aren't and install it
on-the-fly.

I didn't see any diff in the output of `kustomize build config/default`
with `[email protected]` and the redundant `name` fields and with
`[email protected]` without them.

Signed-off-by: Yoni Bettan <[email protected]>

Author: ybettan

config/default-hub/kustomizeconfig.yaml

@@ -1,4 +1,3 @@
 namePrefix:
 - kind: Deployment
-  name: controller
   path: spec/template/spec/volumes/secret/secretName

config/default/kustomizeconfig.yaml

@@ -1,4 +1,3 @@
 namePrefix:
 - kind: Deployment
-  name: controller
   path: spec/template/spec/volumes/secret/secretName

config/webhook-cert/kustomizeconfig.yaml

@@ -18,5 +18,4 @@ varReference:
 namePrefix:
 - kind: Certificate
   group: cert-manager.io
-  name: serving-cert
   path: spec/secretName

hack/download-kustomize

@@ -5,7 +5,7 @@ set -euxo pipefail
 : "$BINDIR"
 
 readonly TMP=$(mktemp -d)
-readonly VERSION=5.3.0
+readonly VERSION=5.4.3
 
 echo "Downloading kustomize in $TMP"