Skip to content

Latest commit

 

History

History
73 lines (70 loc) · 2.33 KB

agent-install-sample-config-bonds-vlans.adoc

File metadata and controls

73 lines (70 loc) · 2.33 KB

Example: Bonds and VLAN interface node network configuration

The following agent-config.yaml file is an example of a manifest for bond and VLAN interfaces.

  apiVersion: v1alpha1
  kind: AgentConfig
  rendezvousIP: 10.10.10.14
  hosts:
    - hostname: master0
      role: master
      interfaces:
       - name: enp0s4
         macAddress: 00:21:50:90:c0:10
       - name: enp0s5
         macAddress: 00:21:50:90:c0:20
      networkConfig:
        interfaces:
          - name: bond0.300 (1)
            type: vlan (2)
            state: up
            vlan:
              base-iface: bond0
              id: 300
            ipv4:
              enabled: true
              address:
                - ip: 10.10.10.14
                  prefix-length: 24
              dhcp: false
          - name: bond0 (1)
            type: bond (3)
            state: up
            mac-address: 00:21:50:90:c0:10 (4)
            ipv4:
              enabled: false
            ipv6:
              enabled: false
            link-aggregation:
              mode: active-backup (5)
              options:
                miimon: "150" (6)
              port:
               - enp0s4
               - enp0s5
        dns-resolver: (7)
          config:
            server:
              - 10.10.10.11
              - 10.10.10.12
        routes:
          config:
            - destination: 0.0.0.0/0
              next-hop-address: 10.10.10.10 (8)
              next-hop-interface: bond0.300 (9)
              table-id: 254
  1. Name of the interface.

  2. The type of interface. This example creates a VLAN.

  3. The type of interface. This example creates a bond.

  4. The mac address of the interface.

  5. The mode attribute specifies the bonding mode.

  6. Specifies the MII link monitoring frequency in milliseconds. This example inspects the bond link every 150 milliseconds.

  7. Optional: Specifies the search and server settings for the DNS server.

  8. Next hop address for the node traffic. This must be in the same subnet as the IP address set for the specified interface.

  9. Next hop interface for the node traffic.