Skip to content

Commit dbfb484

Browse files
faiqdlipovetsky
andauthored
docs: refine wording around updates
Co-authored-by: Daniel Lipovetsky <[email protected]>
1 parent da4e8cb commit dbfb484

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/proposal/20250922-nodeadm-bootstrap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ This KEP proposes a new type that handles bootstrapping with `nodeadm` alone. Th
151151
152152
### Upgrade Strategy
153153
154-
A valid concern that CAPA users will have is upgrading existing clusters to machines that use the new bootstrap `Nodeadm` CRD. This is largely assuaged by CAPI's immutable design where new machines will be deployed by referencing new templates. In summary, upgrading should not be a problem.
154+
A valid concern that CAPA users will have is upgrading existing clusters to machines that use the new bootstrap `Nodeadm` CRD. This KEP does not change the process. As before, the user will reference a new BootstrapConfigTemplate. However, the kind will change from EKSConfigTemplate to NodeadmConfigTemplate.
155155
156156
#### MachineDeployment Upgrade Example
157157

0 commit comments

Comments
 (0)