SnasphotId from tags

[timbgn]

Description

What problem are you trying to solve?
Populate snapshotId of Block Mapping from tags in AWS

How important is this feature to you?
We can work around this currently but feels like it would be nice to have karpenter read the tags of EBS snapshots and select the one matching provided tag values.

We are currently populating some large docker images and baseline pod images to an EBS snapshot and then hub-spoking out to organization accounts. I would like to be able to use our tekton pipeline to shunt the tag for latest snapshot around and have karpenter select that image.

This would open up various options to

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[jonathan-innis]

So you basically want a snapshotSelectorTerm as well that you could reference inside of the blockDeviceMapping? What would you like to happen if this tag happened to select multiple snapshots?

[timbgn]

it is a good question. I could see both caveating the use to be having to select a unique snapshot or defaulting to the latest in CompletionTime of the returned snapshots would work. From my side of things I have been looking at moving a tag in the tekton pipeline we have that generates and copies the snapshot but am also considering having a timestamp of the pipeline run added so that it can be sorted to use the most recent.

[jonathan-innis]

Can the same orchestration that you have in the Tekton pipeline be applied to updating the NodeClass? One high-level question I have is how is this different than directly updating the manifest?