Enabling Service Mesh for Oracle Kubernetes Engine

In a 𝙢𝙞𝙘𝙧𝙤𝙨𝙚𝙧𝙫𝙞𝙘𝙚𝙨 𝙖𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚, monolithic applications are broken down into smaller microservices that 𝙘𝙤𝙢𝙢𝙪𝙣𝙞𝙘𝙖𝙩𝙚 𝙤𝙫𝙚𝙧 𝙩𝙝𝙚 𝙣𝙚𝙩𝙬𝙤𝙧𝙠 using an 𝘼𝙋𝙄.

This causes:
(1) a 𝙨𝙪𝙧𝙜𝙚 𝙤𝙛 𝙣𝙚𝙩𝙬𝙤𝙧𝙠 𝙩𝙧𝙖𝙛𝙛𝙞𝙘 and
(2) increases the 𝙘𝙤𝙢𝙥𝙡𝙚𝙭𝙞𝙩𝙮 and 𝙤𝙫𝙚𝙧𝙖𝙡𝙡 𝙖𝙩𝙩𝙖𝙘𝙠 𝙨𝙪𝙧𝙛𝙖𝙘𝙚 in the architecture.

Adding a 𝙨𝙚𝙧𝙫𝙞𝙘𝙚 𝙢𝙚𝙨𝙝 to the microservices 𝙖𝙡𝙡𝙚𝙫𝙞𝙖𝙩𝙚𝙨 𝙢𝙖𝙣𝙮 𝙤𝙛 𝙩𝙝𝙚 𝙘𝙝𝙖𝙡𝙡𝙚𝙣𝙜𝙚𝙨 introduced with a microservices architecture and provides the 𝙛𝙤𝙡𝙡𝙤𝙬𝙞𝙣𝙜 𝙗𝙚𝙣𝙚𝙛𝙞𝙩𝙨:
(1) 🚦Allows you to 𝙘𝙤𝙣𝙩𝙧𝙤𝙡 the microservices 𝙩𝙧𝙖𝙛𝙛𝙞𝙘 𝙛𝙡𝙤𝙬.
(2) 🔭 Provides 𝙫𝙞𝙨𝙞𝙗𝙞𝙡𝙞𝙩𝙮 into your 𝙖𝙥𝙥𝙡𝙞𝙘𝙖𝙩𝙞𝙤𝙣𝙨.
(3) 🔐 Enables microservices to 𝙘𝙤𝙣𝙣𝙚𝙘𝙩 𝙨𝙚𝙘𝙪𝙧𝙚𝙡𝙮 without any changes to the application code.

𝙊𝘾𝙄 𝙎𝙚𝙧𝙫𝙞𝙘𝙚 𝙈𝙚𝙨𝙝 uses a 𝙨𝙞𝙙𝙚𝙘𝙖𝙧 𝙢𝙤𝙙𝙚𝙡. This architecture:
(1) encapsulates the code implementing the network functionality into a network proxy and then
(2) relies on traffic from and to services to be redirected into the sidecar proxy.

In Oracle 𝙆𝙪𝙗𝙚𝙧𝙣𝙚𝙩𝙚𝙨 𝙀𝙣𝙜𝙞𝙣𝙚 (𝙊𝙆𝙀), the application container sits 𝙖𝙡𝙤𝙣𝙜𝙨𝙞𝙙𝙚 𝙩𝙝𝙚 𝙥𝙧𝙤𝙭𝙮 𝙨𝙞𝙙𝙚𝙘𝙖𝙧 𝙘𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧 𝙞𝙣 𝙩𝙝𝙚 𝙨𝙖𝙢𝙚 𝙥𝙤𝙙. Since they are in the same pod, they share:
(1) the 𝙨𝙖𝙢𝙚 𝙣𝙚𝙩𝙬𝙤𝙧𝙠 𝙣𝙖𝙢𝙚𝙨𝙥𝙖𝙘𝙚 and
(2) 𝙄𝙋 𝙖𝙙𝙙𝙧𝙚𝙨𝙨,
allowing the 𝙘𝙤𝙣𝙩𝙖𝙞𝙣𝙚𝙧𝙨 𝙩𝙤 𝙘𝙤𝙢𝙢𝙪𝙣𝙞𝙘𝙖𝙩𝙚 𝙫𝙞𝙖 “𝙡𝙤𝙘𝙖𝙡𝙝𝙤𝙨𝙩.”

𝙀𝙣𝙖𝙗𝙡𝙚 𝙊𝘾𝙄 𝙎𝙚𝙧𝙫𝙞𝙘𝙚 𝙈𝙚𝙨𝙝 𝙤𝙣 𝙮𝙤𝙪𝙧 𝙆𝙪𝙗𝙚𝙧𝙣𝙚𝙩𝙚𝙨 𝙖𝙥𝙥𝙡𝙞𝙘𝙖𝙩𝙞𝙤𝙣𝙨
https://docs.oracle.com/en/solutions/oci-service-mesh-oke/index.html#GUID-12216A44-2E62-48D8-8C89-864335BE9EF6