The model serving endpoint for the judge model does not always have verified certificates, sometimes they are self-signed. The communication will be encrypted but the certificate security chain won't be valid. Now we have a new --judge-serving-model-ca-cert flag that allows use to use custom certificates when interacting with the judge model serving endpoint.
The secret that holds the judge model serving details can be amended with a new property: JUDGE_CA_CERT: "cm-ca-cert" to point to the ConfigMap that contains the custom certificates bundle.
Signed-off-by: Sébastien Han seb@redhat.com
(cherry picked from commit e1eca22dfa055938de3998ce987af5c9fc6c6962)
The model serving endpoint for the judge model does not always have verified certificates, sometimes they are self-signed. The communication will be encrypted but the certificate security chain won't be valid. Now we have a new
--judge-serving-model-ca-cert
flag that allows use to use custom certificates when interacting with the judge model serving endpoint. The secret that holds the judge model serving details can be amended with a new property:JUDGE_CA_CERT: "cm-ca-cert"
to point to the ConfigMap that contains the custom certificates bundle.Signed-off-by: Sébastien Han seb@redhat.com (cherry picked from commit e1eca22dfa055938de3998ce987af5c9fc6c6962)