Support for Debian Buster

[justaugustus]

A request was made to add support for Debian Buster: #720 (comment)

Buster is scheduled to be released around the same time as Kubernetes 1.15, so this will have to happen during the 1.16 release cycle instead.

/kind feature
/priority important-longterm
/milestone v1.16
/help
/sig release
/area release-eng

[k8s-ci-robot]

@justaugustus: The provided milestone is not valid for this repository. Milestones in this repository: [next, v1.15]

Use /milestone clear to clear the milestone.

In response to this:

A request was made to add support for Debian Buster: #720 (comment)

Buster is scheduled to be released around the same time as Kubernetes 1.15, so this will have to happen during the 1.16 release cycle instead.

/kind feature
/priority important-longterm
/milestone v1.16
/help
/sig release
/area release-eng

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.

[justaugustus]

/milestone v1.16
cc: @praseodym

[praseodym]

Thanks! Creating an issue for this was still on my todo list 🙂

[rkojedzinszky]

Hi All,

I am also waiting for Buster support. One thing I've found, that kubelet repeatedly inserts an iptables rule, which was not the case on debian stretch. I think, https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet_network_linux.go#L64 is responsible for this rule being inserted several times, but I had no time to dig deeper.

Keep up with the great job!

[johscheuer]

@rkojedzinszky you probably stepped into this bug: kubernetes/kubernetes#71305

[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

[justaugustus]

This is kind of a confusing case due to naming.
During the release process, we publish all debs to the following repository: apt.kubernetes.io --> https://packages.cloud.google.com/apt/dists/kubernetes-xenial

In installation instructions like kubeadm, you will see references to kubernetes-xenial, though the packages contained therein are known to work for distributor-supported versions of Debian/Ubuntu.

I'll assign myself here to document that idiosyncrasy.

Eventually, we'll move to repositories that are more aptly-named (pun intended), but there are quite a few things to do before we get to that stage.
You can track that work here:

• Establish Kubernetes build/stage/release process on k8s-infra
• Umbrella issue for a job that signs artifacts and uploads them to a GCS bucket

/remove-help
/assign
/milestone v1.18

[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

[olemarkus]

/lifecycle stale

[olemarkus]

/remove-lifecycle stale

[xmudrii]

@justaugustus Is there any update on this issue? Can we reassign it? I believe that we should move it away from the 1.18 milestone, but I don't have permission to do so.

[justaugustus]

/milestone v1.19

[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

[JulyIghor]

Is it going to happen?

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

[DaDummy]

Does that mean that Kubernetes dropped support for Debian?

[praseodym]

Does that mean that Kubernetes dropped support for Debian?

No, the installation instructions are still fine.

[DaDummy]

So support will be dropped once Debian Stretch is EOL or what does it mean that this issue was closed seemingly without a fix?

[praseodym]

So support will be dropped once Debian Stretch is EOL or what does it mean that this issue was closed seemingly without a fix?

I'm not sure if there's anything left to do, Kubernetes works fine on Debian Buster.