-
Notifications
You must be signed in to change notification settings - Fork 288
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
Clean up airgapped docs #6672
Clean up airgapped docs #6672
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #6672 +/- ##
==========================================
- Coverage 75.63% 75.62% -0.01%
==========================================
Files 473 473
Lines 38219 38234 +15
==========================================
+ Hits 28907 28916 +9
- Misses 7717 7721 +4
- Partials 1595 1597 +2 ☔ View full report in Codecov by Sentry. |
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.
Just a few comments.
- **The upgraded version of the `eksctl anywhere` CLI installed on the Admin machine** | ||
- Docker running on the Admin machine | ||
- At least 80GB in storage space on the Admin machine to temporarily store the EKS Anywhere images locally before importing them to your local registry. Currently, when downloading images, EKS Anywhere pulls all dependencies for all infrastructure providers and supported Kubernetes versions. | ||
- The download and import images commands must be run on an amd64 machine to import amd64 images to the registry mirror. |
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.
Are you saying that the Admin machine (where I believe these commands will be run) must be an amd64 machine? Aren't some macOS machines arm-based? If so, should we note that in Admin machine requirements for someone wanting to do airgapped?
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.
@d8660091 thoughts?
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.
When a user runs "download images" in their admin machine, the "docker pull" will run to pull the images. And since "docker pull" only pull images matching the admin machine's arch, arm64 admin machine will eventually upload only arm64 images to the registry mirror. So admin machine needs to be amd64
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.
So I guess I think the requirement is if you're running in an airgapped environment, you need to have an amd64 admin machine
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 added the following note to the admin machine page
- If you are running in an airgapped environment, the Admin machine must be amd64.
eksctl anywhere import images -i images.tar -r <registryUrl> \ | ||
--bundles ./eks-anywhere-downloads/bundle-release.yaml | ||
``` | ||
>**_NOTE:_** If you are running EKS Anywhere on bare metal, you must configure `osImageURL` and `hookImagesURLPath` in your EKS Anywhere cluster specification with the location of the upgraded node operating system image and hook OS image. For details, reference the [bare metal configuration documentation.]({{< relref "../../getting-started/baremetal/bare-spec/#osimageurl" >}}) |
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've tried to use "Bare Metal" with initial caps, so it looks more like an EKS Anywhere provider, rather than just a reference to a piece of hardware. Right now, the docs are somewhat inconsistent, so maybe we should make a choice.
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.
It's not an official product name so we should not use capitalization. See Vipin's original blog https://aws.amazon.com/blogs/containers/introducing-bare-metal-deployments-for-amazon-eks-anywhere/
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.
Sure. That's your call. We can begin dismantling those as we run into them.
- An existing [Admin machine]({{< relref "../install" >}}) | ||
- Docker running on the Admin machine | ||
- At least 80GB in storage space on the Admin machine to temporarily store the EKS Anywhere images locally before importing them to your local registry. Currently, when downloading images, EKS Anywhere pulls all dependencies for all infrastructure providers and supported Kubernetes versions. | ||
- The download and import images commands must be run on an amd64 machine to import amd64 images to the registry mirror. |
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.
Same question about Admin machine requirements for airgapped as above.
tar -xvf eks-anywhere-downloads.tar.gz | ||
``` | ||
|
||
1. Download the EKS Anywhere image dependencies to the Admin machine. This command may take several minutes (10+) to complete. To monitor the progress of the command, you can run with the `-v 6` command line argument, which will show details of the images that are being pulled. Docker must be running for the following command to succeed. |
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.
Looks like you are assuming they are using another machine besides the Admin machine. Should we say that somewhere in the prerequisites?
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 is the Admin machine ... I'm not sure exactly what you mean by "assuming they are using another machine". We can remove the statement about Docker if that's what's causing the confusion here
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.
No. You fixed the issue by saying that the Admin machine must be amd64 to do airgapped. There was a sentence that you deleted that said that the images commands "need to be run on an amd64 machine to import amd64 images to the registry mirror." It didn't say Admin machine.
Co-authored-by: Chris Negus <[email protected]>
Co-authored-by: Chris Negus <[email protected]>
Co-authored-by: Chris Negus <[email protected]>
note to self need to clarify packages page for configuring PBC
Update: added in commit 9ee91e4 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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 |
/cherry-pick release-0.17 |
@csplinter: once the present PR merges, I will cherry-pick it on top of release-0.17 in a new PR and assign it to you. In response to this:
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. |
@csplinter: #6672 failed to apply on top of branch "release-0.17":
In response to this:
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. |
/cherry-pick release-0.17 |
@chrisnegus: #6672 failed to apply on top of branch "release-0.17":
In response to this:
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. |
/cherry-pick release-0.17 |
@chrisnegus: #6672 failed to apply on top of branch "release-0.17":
In response to this:
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. |
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.