1. 14 Mar, 2019 1 commit
  2. 06 Mar, 2019 1 commit
    • Kyle Larose's avatar
      Use ClusterFirstWithHostNet for nginx dnsPolicy (#340) · db126130
      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
      db126130
  3. 05 Mar, 2019 1 commit
  4. 04 Mar, 2019 1 commit
    • Keshav Varma's avatar
      Use the correct ConfigMap for nginx ingress (#328) · 39b5e8b8
      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.
      39b5e8b8
  5. 01 Mar, 2019 2 commits
  6. 18 Feb, 2019 2 commits
  7. 14 Feb, 2019 1 commit
  8. 13 Feb, 2019 2 commits
  9. 11 Feb, 2019 2 commits
  10. 01 Feb, 2019 4 commits
  11. 31 Jan, 2019 3 commits
  12. 09 Jan, 2019 2 commits
  13. 31 Dec, 2018 1 commit
  14. 30 Dec, 2018 1 commit
    • Dave Finster's avatar
      Adjust default backend targetPort for ingress.yaml (#262) · 426f23aa
      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.
      426f23aa
  15. 14 Dec, 2018 2 commits
  16. 11 Dec, 2018 2 commits
  17. 27 Nov, 2018 4 commits
  18. 26 Nov, 2018 2 commits
  19. 23 Nov, 2018 2 commits
  20. 19 Nov, 2018 4 commits