diff --git a/admin-guide/configuration/networking.md b/admin-guide/configuration/networking.md
index c3ba3f4b..d067420e 100644
--- a/admin-guide/configuration/networking.md
+++ b/admin-guide/configuration/networking.md
@@ -60,6 +60,7 @@ networking::connection::management_network:
   ipv6_method: 'disabled'
 ```
 
+
 So there is the list `networking::connections` which selects the network connections which should be configured.
 
 Then for each connection name listed there needs to be a hash in Hiera named `networking::connection::$CONNECTION_NAME`.
@@ -109,6 +110,41 @@ networking::connection::ipoib_network:
 
 NetworkManager also supports other types like `wifi`, `vpn`, `bridge`, `vlan`, etc. Note that other types than `ethernet` and `ethernet` have so far not been tested. Please contact us if you managed to set up some other network type or need help to do so.
 
+
+### Interface Bonding
+For a bonded interfaces there is an own list named `networking::bondings` which defines which configuration defined in `networking::bonding::$NAME` hashes should be appled:
+
+```
+networking::bondings:
+ - bond0
+
+networking::bonding::bond0:
+  ipv4_method: 'manual'
+  ipv4_address: '%{ipv4_by_dns}/24'
+  ipv4_gateway: '129.129.86.1'
+  ipv6_method: 'ignore'
+  slaves:
+    - 'eno5'
+    - 'eno6'
+  bond:
+    mode: '802.3ad'
+    xmit_hash_policy: 'layer2+3'
+    miimon: '100'
+```
+Feel free to extend the documentation here or provide a link for detailed explanation of the bond options.
+
+By default the connection name is automatically used name of the bonding interface, Still, you can use speaking names instead for the connection if you specifiy the interface name explicitely:
+
+```
+networking::bondings:
+ - psi_network
+
+networking::bonding::psi_network:
+  ifc_name: 'bond0'
+  ipv4_method: 'manual'
+  ...
+```
+
 ### Static Routes
 
 Static routes can be added with the `additional_config` key in the connection settings.