Weave

    Installation

    The following command sets up a cluster using Weave.

    2. kops create cluster \
    3.   --networking weave \
    4.   --yes \
    5.   --name myclustername.mydns.io

    Configuring Weave MTU

    The Weave MTU is configurable by editing the cluster and setting mtu option in the weave configuration. AWS VPCs support jumbo frames, so on cluster creation kOps sets the weave MTU to 8912 bytes (9001 minus overhead).

    Weave allows you to pass command line arguments to weave by adding those arguments to the EXTRA_ARGS environmental variable. This can be used for debugging or for customizing the logging level of weave net.

    1. spec:
    3.     weave:
    4.       netExtraArgs: "--log-level=info"

    Configuring Weave NPC EXTRA_ARGS

    Weave-npc (the Weave network policy controller) allows you to customize arguments of the running binary by setting the EXTRA_ARGS environmental variable. This can be used for debugging or for customizing the logging level of weave npc.

    Note that it is possible to break the cluster networking if flags are improperly used and as such this option should be used with caution.

    The Weave network encryption is configurable by creating a weave network secret password. Weaveworks recommends choosing a secret with . If no password is supplied, kOps will generate one at random.

    1. cat /dev/urandom | tr -dc A-Za-z0-9 | head -c9 > password
    2. kops create secret weavepassword -f password
    3. kops update cluster

    Override Weave image tag

    Weave networking comes with default specs and version which are the recommended ones, already configured by kOps . In case users want to override Weave image tag, thus default version, specs should be customized as follows:

    Weave networking comes with default specs related to CPU/Memory requests and limits, already configured by kOps. In case users want to override default values, specs should be customized as follows:

    1.   networking:
    3.       memoryRequest: 300Mi
    4.       cpuRequest: 100m
    5.       memoryLimit: 300Mi
    6.       cpuLimit: 100m
    7.       npcMemoryRequest: 300Mi
    8.       npcCPURequest: 100m
    9.       npcMemoryLimit: 300Mi