[Karpenter] - AWS EC2 tags

Questions and Answers
, ,
1

Hi :wave: ,

Starting to use Karpenter with Qovery :muscle:

I’ve noticed that all the ec2 instance don’t have same tags. For example we have script to perform some security that rely on the tag aws:eks:cluster-name. But it not present on all of the ec2 mounted by Qovery.

Screenshot 2024-09-12 at 15.41.27
Screenshot 2024-09-12 at 15.41.271600×940 65.7 KB

Screenshot 2024-09-12 at 15.42.15
Screenshot 2024-09-12 at 15.42.151554×1070 67.5 KB

There are some explanations about the difference? or just an oversight?

Thanks :pray:

2

Hello @Mike ,

On our side, we define some custom tags that are added to the default ones. Our custom tags are:

  • ClusterId
  • ClusterLongId
  • OrganizationId
  • OrganizationLongId
  • Region

The aws:eks:cluster-name tag is automatically added by default.

I’ve listed all the tags for the nodes in your cluster, and they all have the aws:eks:cluster-name tag. Could you please provide the name or ID of the node that is missing this tag?

Thank you

3

Hello @Pierre_Gerbelot :wave:,

On these EC2 I do not see the tag:

  • i-02109b05b463dc842 (ip-10-0-25-230.eu-west-1.compute.internal)
  • i-01d2c345ffa9f4fd0 (ip-10-0-84-188.eu-west-1.compute.internal)
  • i-0ff7ca4004c82703b (ip-10-0-88-181.eu-west-1.compute.internal)
  • i-0b782d938b9b513b5 (ip-10-0-44-40.eu-west-1.compute.internal)
  • i-0a1bb0c3a5b953e62 (ip-10-0-48-198.eu-west-1.compute.internal)

On these, it’s ok:

  • i-03622c3dff55e5020 (ip-10-0-48-25.eu-west-1.compute.internal)
  • i-0db042ef6f87c5f77 (ip-10-0-38-69.eu-west-1.compute.internal)

My goal it’s to have a clear and constant tag to search my ec2 belonging to Qovery cluster.

Thanks :pray:

4

@Pierre_Gerbelot

My bad, I see them now :pray:
All is fine, sorry for the disturbing :pray:

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.