Skip to content
  1. 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
  2. Nov 14, 2017
  3. Nov 13, 2017
  4. 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
  5. Nov 06, 2017
    • Chad Swenson's avatar
      Support for disabling apiserver insecure port · 0c7e1889
      Chad Swenson authored
      This allows `kube_apiserver_insecure_port` to be set to 0 (disabled). It's working, but so far I have had to:
      
      1. Make the `uri` module "Wait for apiserver up" checks use `kube_apiserver_port` (HTTPS)
      2. Add apiserver client cert/key to the "Wait for apiserver up" checks
      3. Update apiserver liveness probe to use HTTPS ports
      4. Set `kube_api_anonymous_auth` to true to allow liveness probe to hit apiserver's /healthz over HTTPS (livenessProbes can't use client cert/key unfortunately)
      5. RBAC has to be enabled. Anonymous requests are in the `system:unauthenticated` group which is granted access to /healthz by one of RBAC's default ClusterRoleBindings. An equivalent ABAC rule could allow this as well.
      
      Changes 1 and 2 should work for everyone, but 3, 4, and 5 require new coupling of currently independent configuration settings. So I also added a new settings check.
      
      Options:
      
      1. The problem goes away if you have both anonymous-auth and RBAC enabled. This is how kubeadm does it. This may be the best way to go since RBAC is already on by default but anonymous auth is not.
      2. Include conditional templates to set a different liveness probe for possible combinations of `kube_apiserver_insecure_port = 0`, RBAC, and `kube_api_anonymous_auth` (won't be possible to cover every case without a guaranteed authorizer for the secure port)
      3. Use basic auth headers for the liveness probe (I really don't like this, it adds a new dependency on basic auth which I'd also like to leave independently configurable, and it requires encoded passwords in the apiserver manifest)
      
      Option 1 seems like the clear winner to me, but is there a reason we wouldn't want anonymous-auth on by default? The apiserver binary defaults anonymous-auth to true, but kubespray's default was false.
      0c7e1889
    • Günther Grill's avatar
    • Haiwei Liu's avatar
      Add support cAdvisor (#1908) · ad0cd693
      Haiwei Liu authored
      
      
      Signed-off-by: default avatarHaiwei Liu <carllhw@gmail.com>
      ad0cd693
  6. Nov 05, 2017
  7. Nov 03, 2017
  8. Nov 02, 2017
  9. Nov 01, 2017
  10. Oct 31, 2017
  11. Oct 30, 2017
  12. Oct 27, 2017
  13. Oct 26, 2017
  14. Oct 25, 2017
  15. Oct 24, 2017
  16. Oct 20, 2017
  17. Oct 19, 2017
  18. Oct 18, 2017
  19. Oct 17, 2017
  20. Oct 16, 2017
    • neith00's avatar
      Revert "Update roadmap" (#1809) · 77f1d4b0
      neith00 authored
      * Revert "Debian jessie docs (#1806)"
      
      This reverts commit d78577c8.
      
      * Revert "[contrib/network-storage/glusterfs] adds service for glusterfs endpoint (#1800)"
      
      This reverts commit 5fb6b2ea.
      
      * Revert "[contrib/network-storage/glusterfs] bootstrap for glusterfs nodes (#1799)"
      
      This reverts commit 404caa11.
      
      * Revert "Fixed kubelet standard log environment (#1780)"
      
      This reverts commit b8384685.
      
      * Revert "Add support for fedora atomic host (#1779)"
      
      This reverts commit f2235be1.
      
      * Revert "Update network-plugins to use portmap plugin (#1763)"
      
      This reverts commit 6ec45b10.
      
      * Revert "Update roadmap (#1795)"
      
      This reverts commit d9879d80.
      77f1d4b0
    • Seungkyu Ahn's avatar
      Fixed kubelet standard log environment (#1780) · b8384685
      Seungkyu Ahn authored
      Change KUBE_LOGGING to KUBE_LOGTOSTDERR, when installing kubelet
      as host type.
      b8384685
Loading