Exposing GKE PODs to Apigee

https://www.linkedin.com/posts/mahmoudrabie2004_didabryouabrknowabrthat-google-cloud-activity-6940905239856222209-sh-L?utm_source=linkedin_share&utm_medium=member_desktop_web

Google recently supported an organization that wanted to 𝙚𝙭𝙥𝙤𝙨𝙚 𝙞𝙩𝙨 𝙂𝙤𝙤𝙜𝙡𝙚 𝙆𝙪𝙗𝙚𝙧𝙣𝙚𝙩𝙚𝙨 𝙀𝙣𝙜𝙞𝙣𝙚 (𝙂𝙆𝙀) backend 𝙗𝙚𝙝𝙞𝙣𝙙 𝘼𝙥𝙞𝙜𝙚𝙚 𝙓. A 𝙦𝙪𝙞𝙩𝙚 𝙘𝙤𝙢𝙢𝙤𝙣 𝙖𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚, which most of the users delivering 𝙢𝙤𝙙𝙚𝙧𝙣 𝙬𝙚𝙗 𝙖𝙥𝙥𝙡𝙞𝙘𝙖𝙩𝙞𝙤𝙣𝙨 on Google Cloud tend to build upon.

You could connect 𝘼𝙥𝙞𝙜𝙚𝙚 𝙖𝙣𝙙 𝙂𝙤𝙤𝙜𝙡𝙚 𝙆𝙪𝙗𝙚𝙧𝙣𝙚𝙩𝙚𝙨 𝙀𝙣𝙜𝙞𝙣𝙚 (𝙂𝙆𝙀) backends so that you 𝙬𝙤𝙣’𝙩 𝙝𝙖𝙫𝙚 𝙩𝙤 𝙥𝙚𝙧𝙛𝙤𝙧𝙢 𝙇7 𝙧𝙤𝙪𝙩𝙞𝙣𝙜 in 𝙗𝙤𝙩𝙝 𝙘𝙤𝙢𝙥𝙤𝙣𝙚𝙣𝙩𝙨.

This will likely help you to:
(1) ⏱️ 𝙨𝙖𝙫𝙚 𝙩𝙞𝙢𝙚 (managing way fewer configurations) and
(2) 🚀 reach 𝙗𝙚𝙩𝙩𝙚𝙧 𝙥𝙚𝙧𝙛𝙤𝙧𝙢𝙖𝙣𝙘𝙚𝙨.

When a request comes in, Apigee:
(1) reads the Target Endpoint value and
(2) queries Cloud DNS to get the IP of the application pod.
(3) reaches the pod directly, with no need for additional routing to be configured on the K8s cluster.

Thanks to Federico Preli and Luca Prete for releasing their demo as open-source
https://github.com/google/gke-cloud-dns-tls/

𝘾𝙤𝙣𝙣𝙚𝙘𝙩𝙞𝙣𝙜 𝘼𝙥𝙞𝙜𝙚𝙚 𝙩𝙤 𝙂𝙆𝙀 𝙪𝙨𝙞𝙣𝙜 𝙝𝙚𝙖𝙙𝙡𝙚𝙨𝙨 𝙨𝙚𝙧𝙫𝙞𝙘𝙚𝙨 𝙖𝙣𝙙 𝘾𝙡𝙤𝙪𝙙 𝘿𝙉𝙎
https://cloud.google.com/blog/products/application-modernization/connecting-apigee-to-gke-using-headless-services-and-cloud-dns

𝙎𝙩𝙖𝙮 𝙩𝙪𝙣𝙚𝙙 𝙗𝙮 𝙛𝙤𝙡𝙡𝙤𝙬𝙞𝙣𝙜
https://www.linkedin.com/feed/hashtag/didAbRyouAbRknowAbRthat/