After getting SonarQube up and running on my K8s setup, I started moving my project analysis to that setup. To find out that it is not working at all:

This must be the Ingress because this is the only difference with my old setup. A quick Google search confirmed this. The fix is to add an annotation to the Ingress setup like so:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-test
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: "0"
spec:
rules:
- host: "sonar.app.singel.home"
http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: sonar-service
port:
number: 9000
The nginx.ingress.kubernetes.io/proxy-body-size: "0"
here lifts the limit for all the connections. This fixed the SonarQube analysis:

Yeah..