-
Notifications
You must be signed in to change notification settings - Fork 42
Handle properly hibernated Shoots #148
Handle properly hibernated Shoots #148
Conversation
Thank you for the PR, the feature looks pretty nice. Can we also the total number of hibernated shoots to the output of the |
Do you also want to add the other two points from #135 to the PR as @ialidzhikov has suggested? |
Yup, will add it.
Okay i can rename this PR as WIP for now and to bind it to #135 |
fec67fe
to
8c84459
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR.
Can we adapt the info output to be like?
$ g info
Garden: foo
Shoots:
active: 3
hibernated: 2
total: 5
unscheduled: 0
aws-bar:
active: 3
hibernated: 2
total: 5
8c84459
to
b347b87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Minor nits.
b347b87
to
2d1b359
Compare
2d1b359
to
05ef82d
Compare
05ef82d
to
4021a42
Compare
4021a42
to
9a1e04c
Compare
9a1e04c
to
43209c7
Compare
With #138, gardenctl no longer calls the Shoot kube-apiserver to get the nodes. So the hibernation check here is no longer needed. |
43209c7
to
b4d0c46
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
What this PR does / why we need it:
gardenctl ls shoots
andgardenctl info
command.gardenctl shell
Which issue(s) this PR fixes:
Fixes #135
Special notes for your reviewer:
@ialidzhikov @DockToFuture
Release note: