Hey Lorne, thanks for the information. I have a "standard" instance and I'm migrating to "flex" in order to be able to open direct connections to a Kubernetes cluster. Good to know that this should work!
On Wednesday, January 4, 2017 at 10:25:40 AM UTC-8, Lorne Kligerman wrote: > > As Adam mentioned, this is only possible right now with the flex. However > we do know this is a problem and are working towards a solution for > standard, nothing more to report at this time. > > > On Friday, December 30, 2016 at 1:53:53 PM UTC-8, Nick (Cloud Platform > Support) wrote: >> >> Hey Jitenda, >> >> The Flexible Environment can be used by any user, although of course >> being a beta product, it isn't covered by the same SLA's as other products. >> You should check our documentation including the terms of service >> <https://cloud.google.com/terms/>, service level agreements >> <https://cloud.google.com/terms/sla/>, and the explanation of launch >> stages <https://cloud.google.com/terms/launch-stages>. >> >> Cheers, >> >> Nick >> Cloud Platform Community Support >> >> On Thursday, December 29, 2016 at 9:14:50 AM UTC-5, JITENDRA GANGWAR >> wrote: >>> >>> Thanks Adam for your answer , But as per this documentation >>> <https://cloud.google.com/appengine/docs/flexible/> App Engine flexible >>> environment is still in beta release , can it be used in production ? >>> >>> On Saturday, June 25, 2016 at 2:38:46 AM UTC+5:30, Adam (Cloud Platform >>> Support) wrote: >>>> >>>> You should be able to do this if you use a Flexible Environment >>>> instance, and specify the same network name >>>> <https://cloud.google.com/appengine/docs/flexible/java/configuring-your-app-with-app-yaml#network_settings> >>>> >>>> in the app.yaml that your Compute Engine instance running MySQL is on. It >>>> won't work for Standard Environment instances as they are on separate, >>>> physical networks. >>>> >>>> I say "should" as I haven't played around with this, and there's an >>>> additional layer of network routing from the Docker container the app >>>> lives >>>> in which also has its own local subnet. >>>> >>>> On Friday, June 24, 2016 at 10:43:29 AM UTC-4, Stephen Dunkley wrote: >>>>> >>>>> I have a Java Web application deployed on a Compute Engine instance >>>>> connecting to MySql running on another Compute Engine instance in the >>>>> same >>>>> project. I am able to connect to MySql using the internal IP address >>>>> (jdbc:mysql://10.240.0.4:3306/<db_name>). >>>>> >>>>> If I deploy the same web application to an App Engine instance within >>>>> the same project, I can only connect to the MySql instance via the >>>>> extermal >>>>> IP address (jdbc:mysql://104.196.148.141:3306/<db_name). >>>>> >>>>> If I try to use the internal IP address, I get a Communication Link >>>>> Failure, Permission Denied due to policy. >>>>> >>>>> My question is how do I open up communication between an App Engine >>>>> instance and a Compute Engine instance via an internal IP address? The >>>>> performance is about 5 x faster when using the internal IP address. >>>>> >>>>> Any help would be much appreciated >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/dd0f921f-06ff-49ad-97af-a391b407cde9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
