1. 04 Sep, 2017 1 commit
  2. 31 Aug, 2017 2 commits
  3. 27 Jul, 2017 1 commit
  4. 25 Jul, 2017 2 commits
  5. 24 Jul, 2017 1 commit
  6. 18 Jul, 2017 1 commit
  7. 12 Jul, 2017 1 commit
  8. 06 Jul, 2017 2 commits
  9. 05 Jul, 2017 13 commits
  10. 04 Jul, 2017 1 commit
    • Jason Smith's avatar
      Zipkin as option in Kubernetes (#727) · 15029c9a
      Jason Smith authored
      * Remove namespace object and all zipkin objects (fix kubernetes/kubernetes.github.io#3214)
      
      * moved around some manifests to break out zipkin
      
      * moved down memory requirements for user
      15029c9a
  11. 26 Jun, 2017 5 commits
  12. 20 Jun, 2017 2 commits
    • Carlos León's avatar
    • Carlos León's avatar
      Convert FrontEnd service to LoadBalancer · 3a01f335
      Carlos León authored
      The use of NodePort works great for testing in local but for deploying
      to cloud providers like AWS or GKE, when deploying the front-end service
      as a NodePort, the port does indeed get allocated but no public IP gets
      allocated, making the user to manually create a firewall rule to allow
      incoming traffic to that very specific port. This is quite cumbersome.
      By converting the service to a LoadBalancer, providers like GKE will
      pick the service up, allocate a public IP to it and route all the
      traffice to the corresponding endpoint transparently without user
      intervention.
      3a01f335
  13. 12 Jun, 2017 8 commits