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.
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
Feature 2160 add images subcommand #2303
Feature 2160 add images subcommand #2303
Changes from 7 commits
91118b2
85b810b
0c74bd3
01ba997
3a0ed9a
f3542c5
2adbcd2
eab6fdb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
we shouldn't do this anymore, it's too problematic for multi-arch, as discussed in previous review comments.
we pull straight to containerd in the current version of the node image build
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 also a UX issue that is not thought out here, we should probably have
--pull
vs no--pull
.without
--pull
we should use the local docker stored image or tarball, which makes a predictable experience for locally built imageswith
--pull
+--arch
we can support multi-arch builds--arch
without--pull
should possibly be prohibited or throw a warning, unless the inputs are tarballs not image names.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.
supporting tarballs would make it easier to deal with architectures locally without a registry
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.
we should not be doing this for arbitrary images we're adding, this is a quirk of component images from Kubernetes's own build process.