- 14 Mar, 2019 1 commit
-
-
Miguel Garcia authored
-
- 06 Mar, 2019 1 commit
-
-
Kyle Larose authored
The nginx ingress pod is created with `hostNet: true`. This means that it does not, by default, have access to kuebdns. We need that so that the ingress controller can map things like ExternalName services to internal services. This fixes the problem by setting the dnsPolicy to ClusterFirstWithHostNet. Fixes #339
-
- 05 Mar, 2019 1 commit
-
-
Teh Kok How authored
-
- 04 Mar, 2019 1 commit
-
-
Keshav Varma authored
By default, the ingress installation seems to use a non-existing ConfigMap and having another one that exists but isn't used is confusing. This switches the controller to use the one that microk8s creates.
-
- 01 Mar, 2019 2 commits
-
-
Bill Cassidy authored
-
Konstantinos Tsakalozos authored
-
- 18 Feb, 2019 2 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
- 14 Feb, 2019 1 commit
-
-
Konstantinos Tsakalozos authored
-
- 13 Feb, 2019 2 commits
-
-
Konstantinos Tsakalozos authored
* Reorg of tests, disable prometheus, no dns disable
-
Konstantinos Tsakalozos authored
-
- 11 Feb, 2019 2 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
* Fix ingress on arm64 * Do not test monitoring on arm64
-
- 01 Feb, 2019 4 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
* The Jaeger Operator addon
-
Konstantinos Tsakalozos authored
* Add flunetd addon
-
Konstantinos Tsakalozos authored
* Add prometheus
-
- 31 Jan, 2019 3 commits
-
-
Nick Sandford authored
-
Loukas Leontopoulos authored
Add flag in sudo to preserve user environment when running docker command
-
Yasin Uslu authored
I'm migrating my application from docker-compose to kubernetes. While i was doing that i wanted to add efk stack to the mix. I spent some hours before i realized that i was trying to collect logs from an irrelevant docker daemon :)
-
- 09 Jan, 2019 2 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
- 31 Dec, 2018 1 commit
-
-
assafmendelson authored
-
- 30 Dec, 2018 1 commit
-
-
Dave Finster authored
The containerPort in the default-http-backend deployment is defined as 8080, but the service definition is pointing to 80. When I deployed this, I kept getting unreachable upstream errors from nginx. Making this change corrected the problem, which given the container definition, makes sense.
-
- 14 Dec, 2018 2 commits
-
-
James Wilson authored
-
Konstantinos Tsakalozos authored
-
- 11 Dec, 2018 2 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
- 27 Nov, 2018 4 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
- 26 Nov, 2018 2 commits
-
-
Tim Van Steenburgh authored
-
Antti Kaihola authored
-
- 23 Nov, 2018 2 commits
-
-
Nick Veitch authored
* Add building from source doc * typo
-
Konstantinos Tsakalozos authored
-
- 19 Nov, 2018 4 commits
-
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-
Konstantinos Tsakalozos authored
-