Skip to content
  1. Jan 22, 2018
  2. Jan 09, 2018
  3. Jan 05, 2018
  4. Dec 23, 2017
  5. Dec 22, 2017
  6. Dec 20, 2017
  7. Dec 19, 2017
  8. Dec 12, 2017
  9. Nov 29, 2017
    • unclejack's avatar
      contiv network support (#1914) · e5d353d0
      unclejack authored
      
      
      * Add Contiv support
      
      Contiv is a network plugin for Kubernetes and Docker. It supports
      vlan/vxlan/BGP/Cisco ACI technologies. It support firewall policies,
      multiple networks and bridging pods onto physical networks.
      
      * Update contiv version to 1.1.4
      
      Update contiv version to 1.1.4 and added SVC_SUBNET in contiv-config.
      
      * Load openvswitch module to workaround on CentOS7.4
      
      * Set contiv cni version to 0.1.0
      
      Correct contiv CNI version to 0.1.0.
      
      * Use kube_apiserver_endpoint for K8S_API_SERVER
      
      Use kube_apiserver_endpoint as K8S_API_SERVER to make contiv talks
      to a available endpoint no matter if there's a loadbalancer or not.
      
      * Make contiv use its own etcd
      
      Before this commit, contiv is using a etcd proxy mode to k8s etcd,
      this work fine when the etcd hosts are co-located with contiv etcd
      proxy, however the k8s peering certs are only in etcd group, as a
      result the etcd-proxy is not able to peering with the k8s etcd on
      etcd group, plus the netplugin is always trying to find the etcd
      endpoint on localhost, this will cause problem for all netplugins
      not runnign on etcd group nodes.
      This commit make contiv uses its own etcd, separate from k8s one.
      on kube-master nodes (where net-master runs), it will run as leader
      mode and on all rest nodes it will run as proxy mode.
      
      * Use cp instead of rsync to copy cni binaries
      
      Since rsync has been removed from hyperkube, this commit changes it
      to use cp instead.
      
      * Make contiv-etcd able to run on master nodes
      
      * Add rbac_enabled flag for contiv pods
      
      * Add contiv into CNI network plugin lists
      
      * migrate contiv test to tests/files
      
      Signed-off-by: default avatarCristian Staretu <cristian.staretu@gmail.com>
      
      * Add required rules for contiv netplugin
      
      * Better handling json return of fwdMode
      
      * Make contiv etcd port configurable
      
      * Use default var instead of templating
      
      * roles/download/defaults/main.yml: use contiv 1.1.7
      
      Signed-off-by: default avatarCristian Staretu <cristian.staretu@gmail.com>
      e5d353d0
    • Di Xu's avatar
      de422c82
  10. Nov 23, 2017
    • Bogdan Dobrelya's avatar
      Defaults for apiserver_loadbalancer_domain_name (#1993) · 8aafe643
      Bogdan Dobrelya authored
      
      
      * Defaults for apiserver_loadbalancer_domain_name
      
      When loadbalancer_apiserver is defined, use the
      apiserver_loadbalancer_domain_name with a given default value.
      
      Fix unconsistencies for checking if apiserver_loadbalancer_domain_name
      is defined AND using it with a default value provided at once.
      
      Signed-off-by: default avatarBogdan Dobrelya <bogdando@mail.ru>
      
      * Define defaults for LB modes in common defaults
      
      Adjust the defaults for apiserver_loadbalancer_domain_name and
      loadbalancer_apiserver_localhost to come from a single source, which is
      kubespray-defaults. Removes some confusion and simplefies the code.
      
      Signed-off-by: default avatarBogdan Dobrelya <bogdando@mail.ru>
      8aafe643
  11. Nov 13, 2017
  12. Nov 08, 2017
    • Chad Swenson's avatar
      Master component and kubelet container upgrade fixes · e9f795c5
      Chad Swenson authored
      * Fixes an issue where apiserver and friends (controller manager, scheduler) were prevented from restarting after manifests/secrets are changed. This occurred when a replaced kubelet doesn't reconcile new master manifests, which caused old master component versions to linger during deployment. In my case this was causing upgrades from k8s 1.6/1.7 -> k8s 1.8 to fail
      * Improves transitions from kubelet container to host kubelet by preventing issues where kubelet container reappeared during the deployment
      e9f795c5
  13. Nov 06, 2017
  14. Nov 03, 2017
  15. Nov 02, 2017
  16. Nov 01, 2017
  17. Oct 30, 2017
  18. Oct 25, 2017
  19. Oct 19, 2017
  20. Oct 18, 2017
  21. Oct 16, 2017
  22. Oct 15, 2017
  23. Oct 13, 2017
  24. Oct 11, 2017
  25. Oct 09, 2017
  26. Oct 05, 2017
  27. Sep 27, 2017
Loading