Allow disabling the "Name" tag on EC2 instances

Author: tomasz-sodzawicznyCreated Aug 31, 2026Updated Sep 14, 2026
Labelsfeaturetriage/needs-investigationneeds-triage

Description

What problem are you trying to solve? Currently the tagging controller always sets the "Name" tag on the Karpenter-managed EC2 instances, unless a custom "Name" tag already exists (code).

In my system the well-known "Name" tag causes side-effects in observability (similar to this) and I would like to not have it on those instances at all.

For reference how other projects handle it - Managed Node Groups do not set the Name by default, same with a regular ASG and cluster-autoscaler.

How important is this feature to you? At the moment I do not have a way to workaround the issue, so it's a blocker for our adoption of Karpenter. I believe other organizations may be affected too, as EC2 tags are quite overloaded and "Name" is broadly used and prone for collisions.

The change should be very simple to introduce at the code level in backward compatible way - I'm happy to submit a PR if there is an agreement on introducing it.


  • 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

Source: aws/karpenter-provider-aws