Hi Jerry,
You are being directed to the default backend (expected behavior without a host
header in the request).
If you create an ingress with a host: foo.bar.com you can use
curl -v http://node_ip:30682 -H 'Host: foo.bar.com'
On Wednesday, December 6, 2017 at 11:58:22 PM UTC-3, Jerry Hwang
hello,
looking for your help.
my kubernetes is 1.7.7 on SLES 12 sp3
i followed this guide for nginx ingress install on physical nodes cluster.
https://github.com/kubernetes/ingress-nginx/blob/master/deploy/README.md
All deployed and service details
Name: ingress-nginx
Namespace: ingress-nginx
Awesome :)
On Wednesday, December 6, 2017, bg wrote:
> Worked like a charm. Thank you very much!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop
Worked like a charm. Thank you very much!
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To
There is a similar command for kops, see:
https://github.com/kubernetes/kops/blob/master/docs/cli/kops_export_kubecfg.md
That should do the trick.
On Tuesday, December 5, 2017, bg wrote:
> I have several Kubernetes cluster on GKE, and recently created a cluster
> on AWS.
I've been working on adding network policies to an existing application and
have run into a few issues. I'm currently using the network policy
capabilities within Google Kubernetes Engine.
This was my initial attempt was the following network policy, intended to
allow communication between the
Hi all,
I believe the master of a GKE cluster is upgraded automatically. If so, what is
the criteria for GKE to auto upgrade the master to a newer version? Do all the
node pools of the cluster have to have auto upgrade turned on? If not, is there
some setting that instructs the cluster to auto
As far as I am aware, you cannot change a pod after it has been started. A
pod *can* talk to the Kubernetes API to start more pods, and I believe you
can use node affinity
https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ to make
sure that a new pod gets scheduled where you need