@bgrant0607 I can do more work to improve consistence should I start working on this?

@adohe That would be great, but let's get your existing PRs in and also wait for the initial ReplicaSet implementation to be merged.

I just noticed another inconsistency: job, ingress, daemonset don't have AGE columns.

@bgrant0607 I will add this after these two PRs(#21369, #21295 ) get merged.

Here's the annotation output we use in Origin:

func formatAnnotations(out *tabwriter.Writer, m api.ObjectMeta, prefix string) {
    values, annotations := extractAnnotations(m.Annotations, "description")
    if len(values[0]) > 0 {
        formatString(out, prefix+"Description", values[0])
    }
    formatMapStringString(out, prefix+"Annotations", annotations)
}

We haven't formally defined description (yet) so it's really:

func formatMapStringString(out *tabwriter.Writer, label string, items map[string]string) {
    keys := sets.NewString()
    for k := range items {
        keys.Insert(k)
    }
    if keys.Len() == 0 {
        formatString(out, label, "")
        return
    }
    for i, key := range keys.List() {
        if i == 0 {
            formatString(out, label, fmt.Sprintf("%s=%s", key, items[key]))
        } else {
            fmt.Fprintf(out, "%s\t%s=%s\n", "", key, items[key])
        }
    }
}

We probably want special handling on annotations to deal with very long annotations (trim past a certain length) and to deal with newlines and ansi escape sequences (we may have to strip them)

@smarterclayton ok, I will think about this more.

Meanwhile, for those who find their way here and want a quick workaround kubectl get service $foo -o yaml | grep "key:" is basic and kubectl get service apex-main -o json | jq .metadata.annotations is smarter.

ref #52484

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close