Skip to content
  1. Jun 11, 2019
  2. Jun 05, 2019
  3. May 20, 2019
  4. May 03, 2019
  5. Apr 29, 2019
  6. Apr 15, 2019
  7. Apr 11, 2019
  8. Apr 10, 2019
  9. Apr 04, 2019
  10. Apr 01, 2019
  11. Feb 26, 2019
  12. Feb 12, 2019
  13. Feb 02, 2019
  14. Dec 27, 2018
  15. Dec 18, 2018
  16. Dec 12, 2018
  17. Dec 06, 2018
    • Andreas Krüger's avatar
      Remove non-kubeadm deployment (#3811) · ddffdb63
      Andreas Krüger authored
      * Remove non-kubeadm deployment
      
      * More cleanup
      
      * More cleanup
      
      * More cleanup
      
      * More cleanup
      
      * Fix gitlab
      
      * Try stop gce first before absent to make the delete process work
      
      * More cleanup
      
      * Fix bug with checking if kubeadm has already run
      
      * Fix bug with checking if kubeadm has already run
      
      * More fixes
      
      * Fix test
      
      * fix
      
      * Fix gitlab checkout untill kubespray 2.8 is on quay
      
      * Fixed
      
      * Add upgrade path from non-kubeadm to kubeadm. Revert ssl path
      
      * Readd secret checking
      
      * Do gitlab checks from v2.7.0 test upgrade path to 2.8.0
      
      * fix typo
      
      * Fix CI jobs to kubeadm again. Fix broken hyperkube path
      
      * Fix gitlab
      
      * Fix rotate tokens
      
      * More fixes
      
      * More fixes
      
      * Fix tokens
      ddffdb63
  18. Nov 12, 2018
  19. Nov 10, 2018
  20. Oct 24, 2018
  21. Oct 17, 2018
  22. Oct 16, 2018
    • JuanJo Ciarlante's avatar
      [jjo] add kube-router support (#3339) · a5edd0d7
      JuanJo Ciarlante authored
      * [jjo] add kube-router support
      
      Fixes cloudnativelabs/kube-router#147.
      
      * add kube-router as another network_plugin choice
      * support most used kube-router flags via
        `kube_router_foo` vars as other plugins
      * implement replacing kube-proxy (--run-service-proxy=true) via
        `kube_proxy_mode: none`, verified in a _non kubeadm_enabled_
        install, should also work for recent kubeadm releases via
        `skipKubeProxyInstall: true` config
      
      * [jjo] address PR#3339 review from @woopstar
      
      * add busybox image used by kube-router to downloads
      
      * fix busybox download groups key
      
      * rework kubeadm_enabled + kube_router_run_service_proxy
      
      - verify it working ok w/the kubeadm_enabled and
        kube_router_run_service_proxy true or false
      
      - introduce `kube_proxy_remove` fact, to decouple logic
        from kube_proxy_mode (which affects kubeadm configmap
        settings, thus no-good to ab-use it to 'none')
      
      * improve kube-router.md re: kubeadm_enabled and kube_router_run_service_proxy
      
      * address @woopstar latest review
      
      * add inventory/sample/group_vars/k8s-cluster/k8s-net-kube-router.yml
      
      * fix kube_router_run_service_proxy conditional for kube-proxy removal
      
      * fix kube_proxy_remove fact (w/ |bool), add some needed kube-proxy tags on my and existing changes
      
      * update kube-router tolerations for 1.12 compatibility
      
      * add PriorityClass to kube-router DaemonSet
      a5edd0d7
  23. Oct 11, 2018
  24. Sep 21, 2018
  25. Sep 20, 2018
  26. Sep 19, 2018
  27. Aug 31, 2018
  28. Aug 22, 2018
  29. Aug 21, 2018
  30. Aug 20, 2018
  31. Aug 07, 2018
  32. May 27, 2018
  33. May 22, 2018
  34. May 18, 2018
  35. May 16, 2018
    • Christopher J. Ruwe's avatar
      assert that number of pods on node does not exceed CIDR address range · c1bc4615
      Christopher J. Ruwe authored
      The number of pods on a given node is determined by the  --max-pods=k
      directive. When the address space is exhausted, no more pods can be
      scheduled even if from the --max-pods-perspective, the node still has
      capacity.
      
      The special case that a pod is scheduled and uses the node IP in the
      host network namespace is too "soft" to derive a guarantee.
      
      Comparing kubelet_max_pods with kube_network_node_prefix when given
      allows to assert that pod limits match the CIDR address space.
      c1bc4615
Loading