Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kpt function to analyze OS/Arch info of an image and configure nodeSelector #3386

Open
droot opened this issue Jul 18, 2022 · 0 comments
Open

kpt function to analyze OS/Arch info of an image and configure nodeSelector #3386

droot opened this issue Jul 18, 2022 · 0 comments
Labels
area/fn-catalog Functions Catalog enhancement New feature or request triaged Issue has been triaged by adding an `area/` label

Comments

@droot
Copy link
Contributor

droot commented Jul 18, 2022

Users have kubernetes clusters with different types of nodes (OS, Arch) but the container images they run may only support a subset of OS, Arch. So, package authors usenodeSelector field to appropriate select nodes that support the shipped image, but this can be automated where a kpt function can analyze the OS/Arch info of a container image and customize the nodeSelector.

This highlights the capability of out-of-band bulk automation that is cross-cutting can be done at the platform engineering level.

Linking to the comment for more context: https://github.com/GoogleContainerTools/kpt/pull/3380/files#r923899911
@droot droot added the enhancement New feature or request label Jul 18, 2022
@droot droot mentioned this issue Jul 19, 2022
Merged
@mortent mortent added area/fn-catalog Functions Catalog triaged Issue has been triaged by adding an `area/` label labels Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fn-catalog Functions Catalog enhancement New feature or request triaged Issue has been triaged by adding an `area/` label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mortent @droot