-
Notifications
You must be signed in to change notification settings - Fork 8
Add optional architecture field #3198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 4 commits
1df6f89
8218de7
c945fd9
5a6b51e
b12bc25
eda1af8
b7b7c43
887d2d8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -151,6 +151,15 @@ type Domains struct { | |
| ReplicatedRegistryDomain string `json:"replicatedRegistryDomain,omitempty"` | ||
| } | ||
|
|
||
| // +kubebuilder:validation:Enum=aarch64;x86_64 | ||
| // Architecture represents a supported CPU architecture identifier. | ||
| type Architecture string | ||
|
|
||
| const ( | ||
| ArchitectureAarch64 Architecture = "aarch64" | ||
| ArchitectureX8664 Architecture = "x86_64" | ||
| ) | ||
|
|
||
| // ConfigSpec defines the desired state of Config | ||
| type ConfigSpec struct { | ||
| Version string `json:"version,omitempty"` | ||
|
|
@@ -160,6 +169,13 @@ type ConfigSpec struct { | |
| UnsupportedOverrides UnsupportedOverrides `json:"unsupportedOverrides,omitempty"` | ||
| Extensions Extensions `json:"extensions,omitempty"` | ||
| Domains Domains `json:"domains,omitempty"` | ||
| // Architecture holds the list of CPU architectures supported by this release. | ||
| // If omitted, x86_64 is assumed for backward compatibility. | ||
| // +kubebuilder:validation:Optional | ||
| // +kubebuilder:validation:MinItems=1 | ||
| // +kubebuilder:validation:MaxItems=2 | ||
| // +listType=set | ||
| Architecture []Architecture `json:"architecture,omitempty"` | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should the EC lint command be updated? i can easily see users misspelling this :)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For sure, I can expand the EC lint command to cover this new field and make sure if anything is included with architecture, its either aarch64/amd64 or x86_64/amd64 |
||
| } | ||
|
|
||
| // OverrideForBuiltIn returns the override for the built-in extension with the | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we're using amd64 all over the codebases, let's just stick with that name instead of
X8664? this is a product facing change though, so @ajp-io might have a different opinion.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marccampbell weighed in early on to express that we should use x86_64 and aarch64 instead of amd64 and arm64