Minikube: Release 0.26.0

Created on 29 Mar 2018  路  8Comments  路  Source: kubernetes/minikube

It's been a long time since we've done a full release, so this one will be larger than most. Opening this bug to track the work. We'll aim to get this out Tuesday, 4/3.

cc @r2d4

Some notable changes:

  • Kubernetes 1.10!
  • Switch from localkube to kubeadm by default (this can be disabled with --bootstrapper=localkube)
  • Lots of refactoring of drivers, thanks @anfernee and @afbjorklund
  • Docker change to 17.12 from 17.09
  • Some ISO changes (nested KVM support, calico networking, etc.
  • Many addon upgrades

and more.

lifecyclstale

All 8 comments

@dlorenc : maybe it would be a good idea to include crictl (#2404), in the ISO for 0.26 ?

Thanks! After upgrading cri-o (#2663), it seems to work! Maybe want to add a /etc/crictl.yaml
(i.e. crictl will default to /var/run/dockershim.sock, rather than /var/run/crio/crio.sock)

$ sudo crictl ps
2018/03/30 16:53:42 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/run/dockershim.sock: connect: no such file or directory"; Reconnecting to {/var/run/dockershim.sock <nil>}

This can be avoided by adding a runtime-endpoint: /var/run/crio/crio.sock configuration
https://github.com/kubernetes-incubator/cri-o/blob/master/crictl.yaml when running with cri-o

@afbjorklund : please answer :
does this minikube 0.26.0 support clustered kubernetes (1 master and 2+ nodes) ?
Waitin for an answer to https://github.com/kubernetes/minikube/issues/2658

@runcom @mrunalp thoughts on @afbjorklund suggestion about crictl.yaml ? and suggestion to what version to update to?

@runcom @mrunalp thoughts on @afbjorklund suggestion about crictl.yaml ? and suggestion to what version to update to?

regarding versions, if this release of minikube supports kube 1.10, then the update should be CRI-O v1.10.0.
About crictl, looks ok to me, I use that setting in crictl.yaml (not sure what was the question though)

@alnhk : if you are talking about multi-node, then that is in #2539 (not in 0.26.0)

@runcom : the "question" was if minikube should add a default configuration for crictl ?
So that it will work out-of-the-box (with sudo), instead of just failing to find dockershim.sock

Will do separate PR.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Was this page helpful?
0 / 5 - 0 ratings