I went to issue SONAR-22149 and saw that it solves exactly this problem, but it said it would go into version 10.6 and it didn’t, now it’s saying it will go into version 10.7 and closed the issue, but I haven’t seen the commit on github yet…
Curiously, the badge works with exact same markdown in SonarQube Github README: sonarqube/README.md at master · SonarSource/sonarqube · GitHub. Maybe Github has some additional workarounds built on top of it? There the badge image originates from githubusercontent.com, not from next.sonarqube.com.
Yes, unfortunately the ticket was bumped to our next release (v10.7), but we intend to handle it early on in the development cycle so that we don’t risk another delay. Thanks for your patience.
I am serving the sonarqube in kubernetes, I had this issue and solved it with nginx. Basically I am routing the network via a nginx deployment to the application, I think this settings should be configurable.
Here is my nginx configuration file
server {
listen 443;
location / {
proxy_pass https://1.1.1.1:1111; # use can use domain or ip adress here
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
add_header Cross-Origin-Resource-Policy same-origin;
}
}
I get the happy task of following up to say that our internal demo today included sharing that the CORS policy has been dropped & the change checked in for 10.7! I’m sorry it’s taken so long.
Hello Ann, so when moving from 10.2 to 10.6.1 (within Kubernetes), the issue our users started to get where badge images did not show is related to this? And that fix should be in the next version or so?