Skip to content
  1. Feb 26, 2019
  2. Feb 25, 2019
  3. Feb 21, 2019
    • Frank Ritchie's avatar
      Add flexvolume plugin dir to kubeadm kubelet (#4168) · 9805fb7a
      Frank Ritchie authored
      This was already approved in #4106 but there are CI issues
      with that PR due to references to kubernetes incubator.
      
      After upgrading to Kubespray 2.8.1 with Kubeadm enabled Rook
      Ceph volume provision failed due to the flexvolume plugin dir not
      being correct. Adding the var fixed the issue
      9805fb7a
  4. Feb 20, 2019
  5. Feb 19, 2019
  6. Feb 18, 2019
  7. Feb 14, 2019
    • Chad Swenson's avatar
      Docker apt repo name fix (again) (#4246) · e552be76
      Chad Swenson authored
      For some reason 18.09 packages are now prefixed with `5:` in the download.docker.com apt repos
      Followup to #4236
      e552be76
    • Ryler Hockenbury's avatar
      eea22dfd
    • Maxime Guyot's avatar
      0a722942
    • Kaoet's avatar
    • hikoz's avatar
      use swapon -s (#4216) · e03588f4
      hikoz authored
      e03588f4
    • Chad Swenson's avatar
      Fix calico when kube_override_hostname is set (#4235) · 8872b2e0
      Chad Swenson authored
      This fixes an issue where the `nodename` in calico's cni config json can fall out of sync with the k8s node name used by the calico pod if `kube_override_hostname` is set
      8872b2e0
    • Florent Monbillard's avatar
      Explicitely set etcd endpoint in kubeadm-images.yaml (#4063) · 061f5a31
      Florent Monbillard authored
      Currently, the task `container_download | download images for kubeadm config images` fetches etcd image even though it's not required (etcd is bootstrapped by kubespray, not kubeadm).
      
      `kubeadm-images.yaml` is only a subset of `kubeadm-config.yaml`, therefore ``kubeadm config images pull` will try to get all this list (including etcd)
      
      ```
      # kubeadm config images list --config /etc/kubernetes/kubeadm-images.yaml
      k8s.gcr.io/kube-apiserver:v1.13.2
      k8s.gcr.io/kube-controller-manager:v1.13.2
      k8s.gcr.io/kube-scheduler:v1.13.2
      k8s.gcr.io/kube-proxy:v1.13.2
      k8s.gcr.io/pause:3.1
      k8s.gcr.io/etcd:3.2.24
      k8s.gcr.io/coredns:1.2.6
      ```
      
      When using the `kubeadm-config.yaml` though, it doesn't list etcd image:
      
      ```
      # kubeadm config images list --config /etc/kubernetes/kubeadm-config.yaml
      k8s.gcr.io/kube-apiserver:v1.13.2
      k8s.gcr.io/kube-controller-manager:v1.13.2
      k8s.gcr.io/kube-scheduler:v1.13.2
      k8s.gcr.io/kube-proxy:v1.13.2
      k8s.gcr.io/pause:3.1
      k8s.gcr.io/coredns:1.2.6
      ```
      
      This change just adds the etcd endpoints in the `kubeadm-images.yaml` to give a hint to kubeadm it doesn't need etcd image for its boostrapping as etcd is "external".
      I confess it is a ugly hack, a better way would be to use a single `kubeadm-config.yaml` for both tasks, but they are triggered by different roles (`kubeadm-images.yaml` is used by download, `kubeadm-config.yaml` by kubernetes/master) at different steps and I didn't want to refactor too many things to prevent breakage. 
      
      This is specially useful for offline installation where a whitelist of container images is mirrored on a local private container registry. `k8s.gcr.io/etcd` and `quay.io/coreos/etcd`  are two different repositories hosting the same images but using *different tags*! 
      * coreos/etcd:v3.2.24   
      * k8s.gcr.io/etcd:3.2.24 (note the missing 'v' in the tag name)
      061f5a31
  8. Feb 13, 2019
Loading