Skip to content
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

Handle Karpenter nodes without nodepool #23

Closed
Kavinraja-G opened this issue Nov 3, 2023 · 0 comments · Fixed by #24
Closed

Handle Karpenter nodes without nodepool #23

Kavinraja-G opened this issue Nov 3, 2023 · 0 comments · Fixed by #24
Labels
bug Something isn't working

Comments

@Kavinraja-G
Copy link
Owner

Describe the bug
When the nodes are provisioned without any nodepool, in this case karpenter for example, all nodes are shown under a single AZ without taking account of the actual zones.

Reproduce steps

  1. Spin up nodes using Karpenter
  2. kubectl nodegizmo nodepool

Expected behavior
Nodes should seperated based on AZs though if there is no nodepool associated.

Screenshots

❯ k nodegizmo nodepool
NODEPOOL                          	PROVIDER	REGION   	ZONE      	INSTANCE-TYPE	NODES
Unknown                           	Unknown 	us-east-1	us-east-1a	t3a.small    	ip-10-0-0-93.ec2.internal
                                  	        	         	          	             	ip-10-0-10-158.ec2.internal
                                  	        	         	          	             	ip-10-0-11-132.ec2.internal
                                  	        	         	          	             	ip-10-0-14-108.ec2.internal
                                  	        	         	          	             	ip-10-0-19-158.ec2.internal
                                  	        	         	          	             	ip-10-0-22-210.ec2.internal
                                  	        	         	          	             	ip-10-0-24-21.ec2.internal
                                  	        	         	          	             	ip-10-0-30-193.ec2.internal
                                  	        	         	          	             	ip-10-0-31-180.ec2.internal
                                  	        	         	          	             	ip-10-0-32-151.ec2.internal
                                  	        	         	          	             	ip-10-0-32-179.ec2.internal
                                  	        	         	          	             	ip-10-0-33-207.ec2.internal
                                  	        	         	          	             	ip-10-0-37-144.ec2.internal
                                  	        	         	          	             	ip-10-0-37-55.ec2.internal
                                  	        	         	          	             	ip-10-0-38-99.ec2.internal
                                  	        	         	          	             	ip-10-0-4-128.ec2.internal
                                  	        	         	          	             	ip-10-0-4-53.ec2.internal
                                  	        	         	          	             	ip-10-0-40-105.ec2.internal
                                  	        	         	          	             	ip-10-0-40-11.ec2.internal
                                  	        	         	          	             	ip-10-0-41-98.ec2.internal
                                  	        	         	          	             	ip-10-0-42-88.ec2.internal
                                  	        	         	          	             	ip-10-0-46-105.ec2.internal
generic-2023102107344574640000001e	EKS     	us-east-1	us-east-1b	t3.medium    	ip-10-0-23-172.ec2.internal
                                  	        	         	          	             	ip-10-0-33-54.ec2.internal
                                  	        	         	          	             	ip-10-0-7-138.ec2.internal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant