We should support overlay2

[justinsb]

Probably we should consider making it the default in 1.10 (if it's the default upstream)

cf #4894 and discussion there

[tvi]

As I interpret website: https://docs.docker.com/storage/storagedriver/select-storage-driver/ recommends overlay2 to Stretch and newer? We run default Jessie.

[fejta-bot]

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

[stephanlindauer]

any news/plan regarding overlay2 adoption?

[mikesplain]

/remove-lifecycle stale

This will likely be 1.11 since we haven't gotten enough stretch testing in for this release.

[justinsb]

We actually default to overlay2 on kubernetes 1.11 (and that will be in kops 1.10):
https://github.com/kubernetes/kops/blob/master/pkg/model/components/docker.go#L91-L97

But as @mikesplain said, we're delaying this till 1.11 in the hope of figuring out whether overlay2 is stable on jessie (and maybe making stretch or similar the default for 1.11)

[fejta-bot]

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

[voron]

/remove-lifecycle stale

[tsuna]

I'm curious: why is kops so far behind in terms of base image, Docker version, Kubernetes version? 2019 is almost here and out of the box we get k8s 1.10 / docker 17.03.2-ce (which is super obsolete and buggy) / an old Debian with an old kernel version, etc?

[ms4720]

I'm curious: why is kops so far behind in terms of base image, Docker version, Kubernetes version? 2019 is almost here and out of the box we get k8s 1.10 / docker 17.03.2-ce (which is super obsolete and buggy) / an old Debian with an old kernel version, etc?

because it is a large complex project with a small volunteer staff that has too much to do and not enough time to do it in, just a guess.

[fejta-bot]

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.