tree cf1b55ea8386615a70948f9642f68e52d1a26b5e
parent 1be101e923d0fa67a6a82cd13570f634e71139fc
author Jan Klare <jan.klare@bisdn.de> 1696239125 +0200
committer Jan Klare <jan.klare@bisdn.de> 1696239397 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCAAdFiEEt80lub3VhefUQEYIB81h/G0bP5IFAmUaj0AACgkQB81h/G0b
 P5JrdA/+M+daBST8uXjcQem0TZY7KuiS/TB0IPa09HDToIBnj8IB+feaK6EKBQPp
 TpXLtTJwXQ2i3hM7StRLdY7xWV+OC8m2X6YS8YZw/Yh4UnBKIFwltPRcO3rMadUz
 hzqKY7sKxPBLXK1fDBSz+hPNmclGRqiXS9NVMYQmCeMx2ZxRljV1noqCt+KgNfD4
 gFQDYrmm349H4d7hBQTneH4vOT/JKn4mu0i0i0Gj9E6p/XJxKeEyl7FQm17IStG/
 UFKz6aYheTjEB7jgRsxz6gyKeUSZ6rK7BVEiz3QtE2p7S1bkbavWbwcGKQmQaqRL
 4A1WcM686wq08Xo3od4tsCxFUjZghAcZbg0jUv21Bgs0LrlpuBXiywP2lysx7Exp
 UXByW3KUZ2FEOT6Dlm4y8Z4XdT33ewB2icjBzyCP4PExu0APHUkfPDQUOFCwdOHy
 y1ow0Z9Fc7PgbNS72fbdjp6iEVhQQMjKEN/HqFkube9PX50uBxWQrPmsafVLbnf/
 wZEMQ9UTdElIpyOJGL4xuNmz6zT/gv8UWb+ruXtzB2eGiOBq9ANADZ8iCMr3JazK
 R9GLXRckymFP/1z42eRPCOV6Clq07b/ANOSyrAdTLsNPUvoz19ibSoNHwDg1bY4A
 LjdaOFSH6vzepXt+9T4KXNnv4YEVpvZS4Tb4GNTCuz6wVviOZuc=
 =J9F4
 -----END PGP SIGNATURE-----

remove ValidatingWebhookConfiguration for new ingress controller

* some of the pipelines which are now using the new ingress controller
  show errors like:
  Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": dial tcp 10.96.34.207:443: connect: connection refused
* these errors seem to be related to either a misconfiguration or a
  malfunctioning ingress-nginx admission webhook
* there is a lot of discussion online about this issue, but the
  solution seems to be largely dependent on the k8s version and the
  nginx-ingress installed and it might not be worth investigating a
  proper solution for the EOL kind version currently used
  https://stackoverflow.com/questions/61616203/nginx-ingress-controller-failed-calling-webhook
* the simple workaround for now is to just remove the validation webhook
  and defer the fix to the time when we upgrade and start using a
  maintained k8s and ingress-nginx version

Add a change in jjb/ to trigger a jenkins verification pipeline

Signed-off-by: Jan Klare <jan.klare@bisdn.de>
Change-Id: I5477597766f1b879e841f5e943a34684282cef1c