Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Deal better with IP forwarding being disabled #3280

Open
@bboreham

Description

A colleague was puzzled when their Kubernetes cluster did not work, and the root cause was sysctl net.ipv4.ip_forward set to 0.

I don't think we should universally turn it on, since IP forwarding is a security concern. But the current model of Kubernetes+Weave Net definitely requires it, so at least a warning or exit with error when it is found turned off in the kernel.

Activity

jml

jml commented on Apr 21, 2018

@jml

Probably a separate issue, but I'd also suggest amending https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#pod-network to document that it should be turned on.

jml

jml commented on Apr 21, 2018

@jml

Although @bboreham points out in another forum that the instruction might not be necessary for all distros.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Deal better with IP forwarding being disabled · Issue #3280 · weaveworks/weave