Forge Home

flannel

flannel is a virtual network that gives a subnet to each host for use with container runtimes.

27,122 downloads

20,373 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.0.0 (latest)
  • 1.6.0
  • 1.5.0
  • 1.4.1
  • 1.4.0
  • 1.3.0
  • 1.2.0
  • 1.1.0
  • 1.0.0
  • 0.10.0
  • 0.9.0
released Jan 20th 2017
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet >=3.4.0 <5.0.0
  • , , , , , Debian, Ubuntu

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'cristifalcas-flannel', '2.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add cristifalcas-flannel
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install cristifalcas-flannel --version 2.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: docker, flannel

Documentation

cristifalcas/flannel — version 2.0.0 Jan 20th 2017

flannel

Build Status

This module installs and configures flannel.

Usage:

include flannel

Or:

class { 'flannel':
  etcd_endpoints => "http://${::fqdn}:2379",
  etcd_prefix    => '/coreos.com/network',
}

Or using certificates:

  class { '::etcd':
    ensure                      => 'latest',
    etcd_name                   => $::hostname,
    # clients
    listen_client_urls          => 'https://0.0.0.0:2379',
    advertise_client_urls       => "https://${::fqdn}:2379",
    # clients ssl
    cert_file                   => "${::settings::ssldir}/certs/${::clientcert}.pem",
    key_file                    => "${::settings::ssldir}/private_keys/${::clientcert}.pem",
    trusted_ca_file             => "${::settings::ssldir}/certs/ca.pem",
    # authorize clients
    client_cert_auth            => true,
    # cluster
    initial_cluster             => $initial_cluster,
    listen_peer_urls            => 'https://0.0.0.0:7001',
    initial_advertise_peer_urls => "https://${::fqdn}:7001",
    # peers ssl
    peer_cert_file              => "${::settings::ssldir}/certs/${::clientcert}.pem",
    peer_key_file               => "${::settings::ssldir}/private_keys/${::clientcert}.pem",
    peer_trusted_ca_file        => "${::settings::ssldir}/certs/ca.pem",
    # authorize peers
    peer_client_cert_auth       => true,
  }

  class { '::flannel':
    ensure         => 'latest',
    etcd_endpoints => "http://${::fqdn}:2379",
    etcd_keyfile   => "${::settings::ssldir}/private_keys/${::clientcert}.pem",
    etcd_certfile  => "${::settings::ssldir}/certs/${::clientcert}.pem",
    etcd_cafile    => "${::settings::ssldir}/certs/ca.pem",
    etcd_prefix    => '/coreos.com/network',
  }

Create the etcd node:

    class { '::flannel::etcd_key':
        network   => '172.16.0.0/16',
        subnetmin => '172.16.100.0',

}

Journald forward:

The class support a parameter called journald_forward_enable.

This was added because of the PIPE signal that is sent to go programs when systemd-journald dies.

For more information read here: https://github.com/projectatomic/forward-journald

Usage:

  include ::forward_journald
  Class['forward_journald'] -> Class['flannel']