Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.26.0 #2660

Closed
dlorenc opened this issue Mar 29, 2018 · 8 comments
Closed

Release 0.26.0 #2660

dlorenc opened this issue Mar 29, 2018 · 8 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@dlorenc
Copy link
Contributor

dlorenc commented Mar 29, 2018

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.

@afbjorklund
Copy link
Collaborator

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

@afbjorklund
Copy link
Collaborator

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

@alnhk
Copy link

alnhk commented Apr 3, 2018

@afbjorklund : please answer :
does this minikube 0.26.0 support clustered kubernetes (1 master and 2+ nodes) ?
Waitin for an answer to #2658

@fabiand
Copy link
Contributor

fabiand commented Apr 6, 2018

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

@runcom
Copy link
Contributor

runcom commented Apr 6, 2018

@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)

@afbjorklund
Copy link
Collaborator

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

@afbjorklund
Copy link
Collaborator

@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.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2018
@dlorenc dlorenc closed this as completed Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants