[kubernetes-users] Running a default hello world app on container engine

I have deployed a simple Laravel 5.5 app to a docker container in a Google Compute Engine VM. Accessing the app from the docker container deployed above works fine but when moved to a container engine it is giving permission issues on laravel.log. I have given all permissions to the storage

[kubernetes-users] [ANNOUNCE] Prometheus 2.0 Released

Hello Everyone- ICYMI Prometheus, a fellow CNCF project for container monitoring, has released their v2.0 today. You can learn more from the release from these links: 1. CoreOS post with in-depth benchmarks 2. Project blog

Re: [kubernetes-users] Share the IPC namespace between pods

Are you concerned about perf because you measured it? Or because you suspect it might become a thing later? Are you really sure that your pods will ALWAYS be on the same host? Are your pods 1:1 or 1:N relationships? Could these highly-connected pods just be one bigger pod? To be sure, there's

Re: [kubernetes-users] Share the IPC namespace between pods

How big is the overhead from going through the bridge normally? On Wed, Nov 8, 2017, 19:08 wrote: > Thanks Tim, > > Do you know of any technique(s) to speed up the network between pods > (probably co-located onto the same machine)? Shared memory communication > seems to

Re: [kubernetes-users] Share the IPC namespace between pods

Thanks Tim, Do you know of any technique(s) to speed up the network between pods (probably co-located onto the same machine)? Shared memory communication seems to be a good candidate within pods. On Wednesday, November 8, 2017 at 6:42:39 PM UTC+1, Tim Hockin wrote: > Pods should make very few

Re: [kubernetes-users] Cannot access Ingress from LoadBalancer

Writing that reply made me realize my error. I'm telling my LoadBalancer to listen to 80/443 and route to 8090, but nginx-ingress listens on 80/443. The service that nginx-ingress passes the request to is where port 8090 gets mapped. Sorry for all that :( I'm still learning! -- You received

Re: [kubernetes-users] Cannot access Ingress from LoadBalancer

Correct, that is the Cluster IP of my LoadBalancer service. My Pods are listening on port 8090. I tried to curl port 80 because I figured the LoadBalancer listens on 80 and 443 and directs the request to my nginx-ingress. But I also tried to curl port 8090 from inside a node: "curl

Re: [kubernetes-users] Cannot access Ingress from LoadBalancer

I am assuming 10.59.246.49 is your cluster IP? and port 80 is the service port as defined in the Service.spec.ports[] ? Are your pods actually listening on port 80? Or are they on a different port? On Wed, Nov 8, 2017 at 9:41 AM, bg303 wrote: > Thanks, Tim. That guide

Re: [kubernetes-users] Cannot access Ingress from LoadBalancer

Thanks, Tim. That guide was very informative. I was able to get through a few of these steps: Does the Service have any Endpoints? Yes - verified that three pods were returned Are the Pods working? Verified all three pods are working. Is the kube-proxy working? Yes Is kube-proxy writing

[kubernetes-users] Share the IPC namespace between pods

Currently it is possible to share (shared memory) IPC namespace within pods, but not possible to share between pods. Is this something that will be supported in the future? Or goes against the very design of Kubernetes? What is the general opinion of the Community on this? Thanks, Z -- You

[kubernetes-users] Re: Two Cluster in single node

On Tuesday, November 7, 2017 at 1:39:48 AM UTC-5, sureshel...@gmail.com wrote: > > I am working to configure two kubernetes cluster setup(including binaries > installation) in a single machine, so far, I configured Ethernet adapter to > provide 2 ips, is that possible to go, having two