OCNE: How To Connect From CRIO To Local Private Container Registry Using Insecure Protocol?
(Doc ID 3020836.1)
Last updated on MAY 08, 2024
Applies to:
Oracle Cloud Native Environment (OCNE) - Version 1.8.0 and laterInformation in this document applies to any platform.
Goal
This MOS Note provides detailed steps on how to pull/push images using CRIO from OCNE private container registry using self-signed certs by connecting via insecure protocol. It is recommended that OCNE connect to container registry using secure protocol with proper hostname verification as part of SSL handshake. But there may be some cases where Local container registry is configured with SSL and all the client hostnames/IPs/Domain names were not added as part of the certificates which are generated. In these scenarios, CRIO fails to connect to local container registry with SSL errors as SSL handshake fails as hostname verification fails. Steps in this MOS note can be used to enable insecure protocol to bypass the SSH handshake error when CRIO connects to the local container registry.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |