Default port documentation is not consistent when using https about klar HOT 3 OPEN

With the support of clair V3, the behavior has been moved into a V1-specific function newAPIV1 but the behavior stays the same when using V1.

from klar.

@MichaelPereira thanks for the report, do you remember which port is used by default for https in Clair? AFAIR it's also 6060, but not sure, need to check Calir docs. If so option 1 sounds like a right thing to do. If it's different (like 443) we should use it as a sane default for https.

from klar.

It looks like clair does only expose 6060 by default from what I can see in the Dockerfile, config sample or default config, so using it with 443 for HTTPS is something that people have to explicitly set at other levels like a proxy or load balancer in front of the clair service.

I assume that not that many people would have went through those pains (and integrated it with klar) so far to rule out changing the current behavior for V1 then.

from klar.