|
8 | 8 | # Example: endpoint: "https://192.168.0.1:6443" |
9 | 9 | endpoint: "" |
10 | 10 |
|
| 11 | +# Layer-2 VIP for multi-node setups. When set, the chart emits a |
| 12 | +# Layer2VIPConfig document pinning this IP as a floating address on |
| 13 | +# the node's primary link. MUST equal the host portion of `endpoint` |
| 14 | +# above, otherwise the cluster dials an IP that no node actually |
| 15 | +# claims. Blank by default so the shipped value never silently embeds |
| 16 | +# a wrong VIP — fill in only if you want a VIP. Single-node clusters |
| 17 | +# and external-LB topologies leave it blank. |
| 18 | +# Example: floatingIP: 192.168.0.1 |
| 19 | +floatingIP: "" |
| 20 | + |
| 21 | +# Optional override for the link Layer2VIPConfig is pinned to. When |
| 22 | +# left empty the chart picks the default-gateway-bearing link the |
| 23 | +# node already has (the VLAN sub-interface if one carries the |
| 24 | +# default route, otherwise the physical NIC). Set this when the |
| 25 | +# target link does not yet exist on the live system at first apply |
| 26 | +# — typically a VLAN sub-interface that the same template is about |
| 27 | +# to bring up. Without an override the chart would derive the link |
| 28 | +# from discovery on the bare-metal NIC, pin the VIP there, and the |
| 29 | +# VIP would land on the wrong link once the VLAN comes up. |
| 30 | +# When set, Layer2VIPConfig is emitted unconditionally, even on a |
| 31 | +# totally fresh node where discovery has not yet resolved a default- |
| 32 | +# gateway link. The chart does NOT auto-emit a LinkConfig/VLANConfig |
| 33 | +# for the override link; the operator is responsible for ensuring |
| 34 | +# the link comes up — typically by adding a LinkConfig or VLANConfig |
| 35 | +# document for that link to the per-node body overlay. If no such |
| 36 | +# document brings vipLink up, Layer2VIPConfig will dangle on a |
| 37 | +# non-existent link and the cluster endpoint will be unreachable. |
| 38 | +# Example: vipLink: eth0.4000 |
| 39 | +vipLink: "" |
| 40 | + |
11 | 41 | podSubnets: |
12 | 42 | - 10.244.0.0/16 |
13 | 43 | serviceSubnets: |
|
0 commit comments