Does this help? https://github.com/gyliu513/ingress/tree/4674c0ec691c25b1640064d772c3a74e4337a56b/examples/daemonset/nginx#nginx-ingress-daemonset , this can enable running multiple nginx ingress controllers in one cluster with daemonset.
On Mon, Apr 10, 2017 at 8:28 PM, Matt Snoby <matt.sn...@icloud.com> wrote: > Brandon, > Thanks for taking time to reply. The links you sent unfortunately links > to a dead url. However I”m not talking about running a traefik ingress > controller and a nginx ingress controller. I’m talking about running TWO > nginx ingress controllers at the same time. > > Matt > > > > On Apr 9, 2017, at 11:46 PM, Brandon Philips <brandon.phil...@coreos.com> > wrote: > > You are looking for the Ingress Class annotation. See: https://github.com/ > kubernetes/ingress/tree/master/docs/faq#how-do-i- > disable-an-ingress-controller > > Cheers, > > Brandon > > On Sun, Apr 9, 2017 at 7:57 AM <matt.sn...@gmail.com> wrote: > >> If anyone can point me to documentation on this I would be much >> appreciative. How can I have two or more nginx ingress controllers running >> in the same cluster? >> >> This is the use case: >> I have on AWS an nginx ingress controller where I spin up the controller >> with annotations to front the ELB with a particular cert. This means I >> want ( I think ) the ELB to terminate the TLS and everything behind it to >> be unencrypted HTTP. >> >> That being said I have certain application running in the cluster, such >> as Kibana as an example that I want to just run as HTTPS. Easy enough to >> do with a normal setup, however if I have the ELB terminating the TLS this >> presents a problem. >> >> Another use case would be if I wanted to setup one ingress controller to >> be internal only meaning having a list of white listed IP's. Another >> controller could be open to the world. >> >> Does this configuration currently exist? >> >> Thanks, >> M >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-users+unsubscr...@googlegroups.com. >> To post to this group, send email to kubernetes-users@googlegroups.com. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Kubernetes user discussion and Q&A" group. > To unsubscribe from this topic, visit https://groups.google. > com/d/topic/kubernetes-users/FFt3z5XKP6E/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
