✨ feat(api): add Architecture and NodeInfo types to core API #13248
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Architecturetype andNodeInfostruct to both v1beta1 and v1beta2 core APIsstatus.nodeInfofield on Infrastructure Machine Templates as defined in the Opt-in Autoscaling from Zero proposalBackground
The Opt-in Autoscaling from Zero proposal introduced the concept of scaling from zero replicas, which requires infrastructure providers to expose node capacity and metadata information via a
status.nodeInfofield on Infrastructure Machine Templates.Currently, all CAPI providers following this proposal must either:
This leads to code duplication and potential inconsistencies. This PR centralizes these types so all providers can import and use the same standardized definitions.
You can see the duplication happening in both CAPA and CAPZ so far:
Changes
Architecturetype with constants:amd64,arm64,s390x,ppc64leNodeInfostruct witharchitectureandoperatingSystemfieldsapi/core/v1beta1andapi/core/v1beta2make generateto update generated filesProvider Usage
Test plan
make generatepassesmake testpassesmake lintpasses (Go linting; Dockerfile lint requires Docker daemon)🤖 Generated with Claude Code