Closed namejsjeongkr closed 9 months ago
This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
I'm looking forward to your reply
where does the Karpenter controller pods run in your cluster, are they deployed on EKS Fargate?
Thanks for replying my case. No. I deployed on EKS EC2 Instances.
Ok, and how did that instance get created
@bryantbiggs When I created an EKS cluster, I provisioned two Managed NodeGroups. Nodes that are subsequently created are set up to be provisioned through Karpenter.
So, When I tried to upgrade EKS Cluster, there was a mix of instances created through Managed NodeGroup and Karpenter.
ah ok - now I think I (might) know the issue. eksupgrade
is looking for the parent ASG of each instance but it won't find any for Karpenter nodes, got it!
ah ok - now I think I (might) know the issue.
eksupgrade
is looking for the parent ASG of each instance but it won't find any for Karpenter nodes, got it!
I'm curious about it.. As far as I know, Karpenter is developed by AWS. Why didn't you consider this function ? You know, Karpenter doesn't use ASG(Auto Scaling Group) to provision EC2 instances.
This project was developed by previous colleagues long before Karpenter existed so I suspect that plays a large factor
@bryantbiggs, I appreciate your reply. I totally understood what you're saying and I'm looking forward to develop feature to upgrade smoothly Karpenter nodes.
This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
@bryantbiggs, Is there anything to update for me ? If you're too busy to develop this feature, I could help you !
This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
I'll develop the function and post Pull Request.
This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
Expected Behaviour
I tried to upgrade via eksupgrade CLI from 1.25 to 1.26.
Unfortunately, I've got an error about checking node group stage. I created EKS Cluster via Terraform and there's no issues about it.
And the instance where the error occurred is an instance created through Karpenter.
As far as I know, Karpenter doesn't generate nodes via ASG, do I need an ASG name to use the eksupgrade CLI ?
Please let me know what's the best way to upgrade EKS Cluster that in using Karpenter via eksupgrade CLI.
Current Behaviour
Code snippet
Possible Solution
No response
Steps to Reproduce
eksupgrade --force 1.26 ap-northeast-2
Amazon EKS upgrade version
1.26
Python runtime version
3.11
Packaging format used
PyPi
Debugging logs