search

kubecost / cluster-turndown

Automated turndown of Kubernetes clusters on specific schedules.
Apache License 2.0
259 stars 23 forks source link

AWS EKS - Self managed nodegroups / Unmanaged nodegroups #33

Closed brianrudolf-ep closed 3 years ago

brianrudolf-ep commented 3 years ago

Hi there! I'm just trying out this project, and I see the note that AWS EKS requires managed nodegroups for the turndown service to work.

I'm curious if there is a work around for self managed nodes or if there isn't a way to run the service without that functionality.

I've installed everything per the instructions and this is the error message I get when it attempts to Turn Down:

main.go:118]                  Running Kubecost Turndown on: ip-X-X-X-X.us-west-2.compute.internal                                                                                                                                                            
clusterprovider.go:9          Found ProviderID starting with "aws", using AWS Provider                         
provider.go:63]               Found ProviderID starting with "aws", using AWS Provider                                                                                                                                                                         
validator.go:41]              Validating Provider...                                                                                                                                                                                                          
namedlogger.go:48]            [Error] Image Location: InvalidAMIID.NotFound: The image id '[ami-08e89be32f916757b]' does not exist status code: 400, request id: 90e7bf93-ee83-41c0-a5f5-7d89192aa4c7
reflector.go:122]             Starting reflector *v1alpha1.TurndownSchedule (30s) from pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98                                                                               
reflector.go:160]             Listing and watching *v1alpha1.TurndownSchedule from pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98                                                                                   
schedulecontroller.go:109]    Starting TurndownSchedule controller                                                                                                                                                                                  
namedlogger.go:24]            [TurndownScheduler] Schedule Created: &{Current:scaledown ScaleDownID:410612c9-98a3-4006-9c01-a1b1090db209 ScaleDownTime:2021-05-13 18:50:00 +0000 UTC ScaleDownMetadata:map[repeat:daily type:scaledown] ScaleUpID:6e995feb- 
event.go:258]                 Event(v1.ObjectReference{Kind:"TurndownSchedule", Namespace:"", Name:"example-schedule", UID:"b1c9193d-8091-493d-9c00-c60c889ab4df", APIVersion:"kubecost.k8s.io/v1alpha1", ResourceVersion:"3231589", FieldPath:""}): type: 'Norm 
turndownscheduler.go:404]     -- Scale Down --                                                                                                                                                                                                       
namedlogger.go:24]            [TurndownScheduler] Turndown Pod does not exist on expected host node. Preparing environment...                                                                                                                               
namedlogger.go:24]            [Turndown] Creating or Getting the Target Host Node...                                                                                                                                                                        
namedlogger.go:48]            [Error] Failed to prepare current turndown environment. Cancelling. Err=Failed to locate master node in standard turndown strategy.                                                                                           
scheduler.go:188]             Job was cancelled: 6e995feb-69fc-4a0c-bef4-6137490156ff                                                                                                                                                                        
namedlogger.go:24]            [TurndownScheduler] Turndown Schedule Successfully Cancelled                                                                                                                                                                  
schedulecontroller.go:189]    TurndownSchedule 'example-schedule' in work queue no longer exists
mbolt35 commented 3 years ago

Hey @brianrudolf-ep There isn't support for self-managed EKS nodes currently

brianrudolf-ep commented 3 years ago

Thanks for confirming!

dwbrown2 commented 3 years ago

@mbolt35 do you want to leave this open as a potential future feature to support?