To make FlytePropeller trust your IdP provider's certificate, you need to ensure that the IdP's public root certificate is available in the FlytePropeller container's certificate store. This is necessary if your IdP uses a custom or self-signed CA. You can achieve this by mounting the CA certificate into the FlytePropeller pod and updating the container's trust store accordingly. For example, you may mount the certificate as a Kubernetes secret or config map and reference it in your pod spec, ensuring FlytePropeller can validate the IdP's TLS connection. This approach is confirmed by user reports and discussions in the Flyte community regarding certificate issues with IdP integration and FlytePropeller connectivity, especially when using self-signed or private CA certificates ([Docs] Additional Keycloak configuration settings, comment section; [Docs] OAuth with self-signed certificate throws cert error. Security docs need to be updated to reflect this requirement).
Would you like more detail on how to mount the certificate or update the trust store in your FlytePropeller deployment?
Sources:
-
https://github.com/flyteorg/flyte/issues/2606 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.