[Feature] Improvement Proposal for kubectl
Custom Columns of etcd
Resources
#453
Labels
kind/enhancement
Enhancement, improvement, extension
status/closed
Issue is closed (either delivered or triaged)
Feature (What you would like to be added):
I am not certain, what exactly the
etcd
resourceREADY
column in thekubectl
output depicts and find it confusing. At first, I was confused why all 3 pods must be ready for theetcd
resource to become ready. What I care for as an operator is that the quorum is given and theetcd
cluster is available/can serve requests. Only with second priority, I like to know what the state of thepods
is, but for that I can also take a look at them directly or thestatefulset
. I saw that theetcd
resource has aQuorate
condition, which is probably what I am looking for. I would prefer to see that over theAllMembersReady
condition. When I think about it, showing theBackupSucceeded
condition would also make sense and not widen thekubectl
output too much.Then I noticed, that in some cases, it doesn't even mean what I thought it means, e.g. when I worked through the permanent quorum loss runbook, I noticed that my
etcd
resource isREADY=false
while it runs with 1 perfectlyready
replica (before I need to scale it out to 3), even thoughetcd
was up an serving requests just fine (I tested it withetcdctl
).I found that confusing and would welcome the following change:
Quorate
andBackupSucceeded
conditions as columns in thekubectl
outputMotivation (Why is this needed?):
As operator, I care more for those 2 conditions, then for the readiness condition, which I can look up also directly via
pods
or thestatefulset
.The text was updated successfully, but these errors were encountered: