You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update Bare Metal documentation with new IPAM templating logic (#10339)
Updated the TinkerbellTemplateConfig examples in the Advanced Bare Metal
cluster configuration section to reflect the current static IPAM logic:
Changes for Ubuntu template:
- Removed deprecated STATIC_NETPLAN environment variable
- Added CONTENTS field with Go template expressions to directly configure
netplan using Hardware object metadata
- Supports both VLAN and non-VLAN configurations with conditional logic
- Uses netmaskToCIDR template function for proper CIDR notation
Changes for Red Hat Enterprise Linux template:
- Removed deprecated STATIC_NETPLAN environment variable
- Added CONTENTS field with NetworkManager configuration
- Updated DEST_PATH to /etc/NetworkManager/system-connections/static-connection.nmconnection
- Updated MODE to 0600 for NetworkManager connection files
- Supports both VLAN and non-VLAN configurations with conditional logic
- Uses netmaskToCIDR template function for proper CIDR notation
Additional improvements:
- Added important note about template regeneration during EKS-A upgrades
- Emphasized that default templates may change between versions
- Recommended best practice to regenerate templates before customization
- Minor formatting improvements to metadata URLs and datasource content
These changes align the documentation with the current implementation
introduced in PR #10163 and help users avoid common mistakes when
customizing templates across EKS-A version upgrades.
Now you can add your own Actions for configuring nodes. We highly recommend that you do not modify the first and the last Actions in the default `TinkerbellTemplateConfig`. The first Action streams the OS image to the disk, and the last Action reboots the node. See the upstream Tinkerbell documentation for more information on [Templates](https://tinkerbell.org/docs/concepts/templates/) and [Actions](https://tinkerbell.org/docs/concepts/templates/#actions).
392
392
393
+
>**_IMPORTANT:_** When upgrading to a new EKS Anywhere version, the default template structure may change to incorporate improvements or support new features. Before customizing a template for use with a new EKS Anywhere version, always regenerate the default template using the command above to ensure you have the latest template structure. Failure to use an updated template during upgrades may result in provisioning failures or unexpected behavior. It is recommended to regenerate and review the default template with each EKS Anywhere version upgrade, then reapply your customizations to the updated template.
394
+
393
395
The following shows the default `TinkerbellTemplateConfig` generated by `eksctl anywhere generate tinkerbelltemplateconfig`.
394
396
395
397
### Ubuntu
@@ -415,13 +417,50 @@ spec:
415
417
name: stream image to disk
416
418
timeout: 600
417
419
- environment:
420
+
CONTENTS: |
421
+
{{ if (index .Hardware.Interfaces 0).DHCP.VLANID }}network:
0 commit comments