Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v2.28.0
  • v2.27.0
  • v2.25.1
  • v2.24.3
  • v2.26.0
  • v2.24.2
  • v2.25.0
  • v2.24.1
  • v2.22.2
  • v2.23.3
  • v2.24.0
  • v2.23.2
  • v2.23.1
  • v2.23.0
  • v2.22.1
  • v2.22.0
  • v2.21.0
  • v2.20.0
  • v2.19.1
  • v2.18.2
21 results

control-plane

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    MRoci authored
    follow new naming conventions for gcr's coredns image.
    starting from 1.21 kubeadm assumes it to be `coredns/coredns`:
    this causes the kubeadm deployment being unable to pull image, beacuse `v`
    was also added in image tag, until the role `kubernetes-apps` ovverides
    it with the old name, which is only compatible with <=1.7.
    
    Backward comptability with kubeadm <=1.20 is mantained checking
    kubernetes version and falling back to old names (`coredns:1.xx`) when
    the version is less than 1.21
    a0ee5690
    History
    Name Last commit Last update
    ..