ingress-nginx-helm

History

Wesley Hartford 44d7008126 Fix arguments to match replication controller The DaemonSet as it exists causes the pod to crash on startup with the following: Error syncing pod, skipping: failed to "StartContainer" for "nginx-ingress-lb" with RunContainerError: "runContainer: API error (500): Cannot start container 7eab41694a7d817665337724b5710bd17d7846f0212408aa9d6056e3211447a4: [8] System error: exec: \"/nginx-ingress-controller-lb\": stat /nginx-ingress-controller-lb: no such file or directory\n" Modifying the arguments to match the replication controller works.	2016-04-06 09:16:55 -07:00
..
as-daemonset.yaml	Fix arguments to match replication controller	2016-04-06 09:16:55 -07:00
README.md	Remove examples from the main README.md	2016-03-29 19:15:03 -03:00

Wesley Hartford 44d7008126 Fix arguments to match replication controller

The DaemonSet as it exists causes the pod to crash on startup with the following:

Error syncing pod, skipping: failed to "StartContainer" for "nginx-ingress-lb" with RunContainerError: "runContainer: API error (500): Cannot start container 7eab41694a7d817665337724b5710bd17d7846f0212408aa9d6056e3211447a4: [8] System error: exec: \"/nginx-ingress-controller-lb\": stat /nginx-ingress-controller-lb: no such file or directory\n"

Modifying the arguments to match the replication controller works.

2016-04-06 09:16:55 -07:00

as-daemonset.yaml

Fix arguments to match replication controller

2016-04-06 09:16:55 -07:00

README.md

Remove examples from the main README.md

2016-03-29 19:15:03 -03:00

README.md

In some cases could be required to run the Ingress controller in all the nodes in cluster. Using DaemonSet it is possible to do this. The file as-daemonset.yaml contains an example

kubectl create -f as-daemonset.yaml