-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update images.md #16454
Update images.md #16454
Conversation
include explicit instructions on pulling arm64-based images
Welcome @esbc-disciple! |
Hi @esbc-disciple. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
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.
Hi @esbc-disciple, thank you for trying to add more info on how to use ARM64. Nice to see such initiative. I added a few comments. Please take a look.
docs/operations/images.md
Outdated
@@ -1,8 +1,8 @@ | |||
# Images | |||
|
|||
As of Kubernetes 1.27 the default images used by kOps are the **[official Ubuntu 22.04](#ubuntu-2204-jammy)** images. | |||
As of Kubernetes 1.27 the default images used by kOps are the x86_64 (amd64) **[official Ubuntu 22.04](#ubuntu-2204-jammy)** images. If you want to pull the default kOps image, but for an arm64 processor architecture, you can specify an arm64-based instance name in the --control-plane-size and --node-size parameters of the kops create cluster command. |
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.
The topic here is how to find the right images and I don't think this change adds more clarity.
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.
I agree, especially in light of the edits you made to commands, adding a wildcard in the proc-architecture position of the search string.
My thought process in adding this note was to try to help folks bring up their ARM64 instances without editing config (which is super helpful when you are just getting started and learning). I am OK with it being nixed, nonetheless. With the edit to the search strings, folks should be able to read between the lines on how to instantiate ARM images.
docs/operations/images.md
Outdated
@@ -84,6 +84,15 @@ aws ec2 describe-images --region us-east-1 --output table \ | |||
--filters "Name=name,Values=al2023-ami-2*-kernel-6.1-x86_64" |
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.
This should offer the same value as adding a new command for ARM64.
I suggest this approach, instead of new commands.
--filters "Name=name,Values=al2023-ami-2*-kernel-6.1-x86_64" | |
--filters "Name=name,Values=al2023-ami-2*-kernel-6.1-*" |
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.
Yes. This is a Homer Simpson d'oh moment on my part! The way you suggested is much cleaner.
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.
Happens some times to me too... 😆
Please apply this in all the cases and all other suggestions.
make image search commands processor-architecture-agnostic Co-authored-by: Ciprian Hacman <ciprian@hakman.dev>
change image search strings to also capture arm process architecture
Co-authored-by: Ciprian Hacman <ciprian@hakman.dev>
I committed the changes we discussed. Let me know if I need to do anything else. Thank you for making it easy to suggest changes! |
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.
Thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
include explicit instructions on pulling arm64-based images