-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug] propagateASGTags option not working #5420
Comments
I faced the same issue on AWS EKS 1.22 |
Thanks for the issue. Will verify. |
same here with:
I don't really understand the codebase, but it looks like https://github.com/weaveworks/eksctl/pull/5286/files this doesn't address the propagation which is now broken/missing |
so workaround like this:
|
The code propagates TAGS. Not labels or taints. So if you want tags to be propagated to the ASG you need to define tags. tags:
k8s.io/cluster-autoscaler/node-template/label/my-cool-label: pizza |
the problem is that it doesn't propagate these tags to the underlying auto scaling group - they only get correctly added to the eks tags listing what is shown in the screenshot above. So the tags are kinda worthless because they are not pushed to the auto scaling group this was already asked in #4965 which was closed, please the comment #4965 (comment) which says "So yeah, this ticket isn't a duplicate, it's what #3793 (comment) was actually requesting." So it was also requested in that #3793, but closed. so to reiterate: eks nodegroup tags need to be propagated all the way to the ASG, now they are only set to eks nodegroups, but not to the underlying ASGs. please see my script above how I workaround this. |
That screenshot is from the ASG. |
okay, I'll try to make my own screenshots soon |
ok, so this extension of eksctl doesn't deliver what we hoped, right? But I run into another thing when trying to follow the docs not sure what I am doing wrong:
When I run: |
What do you mean? It's exactly what it's supposed to do.:) Propagate tags to the ASG. As the value suggests. The thing you are looking for is for unmanaged nodegroups. Managed nodegroups are just tagged with set tags. Read more here: #1571 |
Please open a separate ticket. |
@youwalther65 you have the yaml wrong
^-- yaml turns so
|
The is disabled for a purpose. We didn't want random tags to be attached on to the EC2. If you have a case for it to happen, please open a separate issue and we can triage it. Thanks. :) |
Ok, I understand that automatic tagging for labels and taints works only with unmanaged nodegroups. However, the documentation for this feature refers to both managed and unmanaged nodegroups, which is very misleading and needs to be corrected. |
@YDKK That's true. Thanks for bringing that up. We'll fix that oversight. |
I just opened this feature request: |
I also just noticed that tags set in the configuration file only get applied to the autoscaling group if you set |
@Skarlso it's not propagating. - name: ng-2
instanceType: m6i.12xlarge
desiredCapacity: 0
minSize: 0
maxSize: 4
availabilityZones: ["us-east-1b"]
tags:
k8s.io/cluster-autoscaler/node-template/label/runtime: caspiandb-containerd
overrideBootstrapCommand: |
#!/bin/bash
set -e
/etc/eks/bootstrap.sh dev --container-runtime containerd --kubelet-extra-args '--node-labels=runtime=caspiandb-containerd' In our case, it means that AWS |
The above config doesn't have propagateAsgTags set to true? |
It was the default... |
Sorry, not following. |
It was true by default not a long time ago. |
I don't recall. :) You might be right, I worked on a lot of other things. However, right now, it's false by default. :) I can't see any changes to the doc saying otherwise. But I might be wrong. :)) |
We will investigate this issue and also check the default setting for |
I just tested all these scenarios with eksctl Unmanaged Nodegroups
Managed Nodegroups
Conclusions
Apologies for any confusion. We'll be updating the documentation to reflect the current code as clearly as possible. I'm looking into why we have not added support for this for managed nodegroups as well given the previous requests. |
Added a PR to update the docs to reflect the current state of eksctl. Hopefully this makes things clearer regarding the difference between managed vs unmanaged nodegroups. It also clears up the behaviour of Lastly, I opened an issue so that |
What were you trying to accomplish?
Attempted to automatically apply label and taint tags to ASGs using the
propagateASGTags
option.I expected the following tags to be created to the ASGs automatically:
k8s.io/cluster-autoscaler/node-template/label/my-cool-label: pizza
k8s.io/cluster-autoscaler/node-template/taint/feaster: "true:NoExecute"
What happened?
The ASGs created are not tagged for labels and taints.
How to reproduce it?
Create a cluster using the following configuration and
eksctl create cluster -f test.yaml -v 4
command.Logs
Anything else we need to know?
Windows 11 Pro 21H2 Build 22000.675
Used scoop command for install eksctl.
Default AWS profile.
Versions
The text was updated successfully, but these errors were encountered: