Score:0

GKE pods unable to resolve Cloud DNS CNAME record and unable to connect to services outside vpc

er flag

Currently I have a GKE and GCE setup in the same VPC and for some reason I'm able to resolve the CNAME record in Cloud DNS as well as connect to that service from the GCE (the service locate in AWS and we already have a VPN between those 2 VPCs). But when I do the same on a pod in GKE , it unable to resolve CNAME record, it still able to resolve A record just fine. And also it unable to connect to that service located in AWS as well. I have already whitelist both the subnet IP of the GCE as well as the GKE.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.