Kubectl: additionalPrinterColumns for CRD's doesn't work in k8s 1.11 for columns with array data

Created on 3 Aug 2018 · 27Comments · Source: kubernetes/kubectl

Kubernetes version (use kubectl version): 1.11 (server-side printing)

Environment:

Cloud provider or hardware configuration: GKE

Bug
Reproduce using the following steps:

1) Create CRD:

crd.yaml

apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: foos.example.istio.io
spec:
  group: example.istio.io
  names:
    kind: Foo
    listKind: FooList
    plural: foos
    singular: foo
  scope: Namespaced
  version: v1alpha1
  additionalPrinterColumns:
  - JSONPath: .spec.servers[*].hosts
    name: hosts
    type: string

$ kubectl apply -f crd.yaml



md5-c237102ae792555cab81c282f3565a7f



apiVersion: example.istio.io/v1alpha1
kind: Foo
metadata:
  name: foo0
spec:
  servers:
  - hosts:
    - foo.example.com
    - bar.example.com
  - hosts:
    - baz.example.com



md5-27feebd274c11692719a7f144928bc51



$ kubectl apply -f crd-instance.yaml



md5-72ff3338feeebb78d96d2264e06b65f1



$ kubectl get foos foo0
NAME      HOSTS
foo0      [foo.example.com bar.example.com]



md5-b04e230223289d9b518b222871bc4a10



$ kubectl get foos foo0 -o jsonpath='{.spec.servers[*].hosts}'
[foo.example.com bar.example.com] [baz.example.com]

arekubectl kinbug prioritP2 sicli

Source

seans3

👍2

Most helpful comment

/remove-lifecycle stale

Ping

howardjohn on 9 Feb 2021

👍2

All 27 comments

created a PR: https://github.com/kubernetes/kubernetes/pull/67079

nikhita on 7 Aug 2018

/kind bug
/area kubectl
/priority P2

seans3 on 26 Sep 2018

/assign @nikhita

seans3 on 26 Sep 2018

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

fejta-bot on 25 Dec 2018

/remove-lifecycle stale

On Tue, Dec 25, 2018 at 6:44 AM fejta-bot notifications@github.com wrote:

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
https://github.com/fejta.
/lifecycle stale

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubectl/issues/517#issuecomment-449782966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXA0CWRC1GdVp2uJ9bZeNvhmJJI45Npks5u8XvsgaJpZM4VukCs
.

nikhita on 25 Dec 2018

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

fejta-bot on 25 Mar 2019

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

fejta-bot on 24 Apr 2019

/remove-lifecycle rotten

seans3 on 24 Apr 2019

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

fejta-bot on 23 Jul 2019

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

fejta-bot on 22 Aug 2019

/remove-lifecycle rotten

seans3 on 22 Aug 2019

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

fejta-bot on 21 Sep 2019

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot on 21 Sep 2019

This is still happening with v1.16.8

obj.yaml

apiVersion: "k8s.josegomez.io/v1"
kind: StorageClusterPair
metadata:
  name: primary-dr
spec:
  remoteSites:
    - name: dr1
    - name: dr2

crd.yaml

[...]
      additionalPrinterColumns:
        - name: Sites
          type: string
          priority: 0
          jsonPath: .spec.remoteSites[*].name
          description: Remote sites enabled.
        - name: Age
          type: date
          jsonPath: .metadata.creationTimestamp

kubectl get storageclusterpair primary-dr

NAME         SITES   AGE
primary-dr   dr1     6m35s

kubectl get storageclusterpair primary-dr -o jsonpath='{.spec.remoteSites[*].name}'

dr1 dr2

pipoe2h on 26 Apr 2020

/reopen

brianpursley on 26 Apr 2020

@brianpursley: Reopened this issue.

In response to this:

/reopen

k8s-ci-robot on 26 Apr 2020

/remove-lifecycle rotten
/assign

brianpursley on 27 Apr 2020

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

fejta-bot on 13 Sep 2020

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

fejta-bot on 13 Oct 2020

This still happens on 1.18

howardjohn on 10 Nov 2020

/remove-lifecycle rotten

eddiezane on 10 Nov 2020

I've narrowed this down to here.

I can take a stab at a fix but I'm not sure if this was intentional or not.

Maybe @smarterclayton or @sttts have insight?

eddiezane on 11 Nov 2020

/assign @seans3

eddiezane on 11 Nov 2020

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-contributor-experience at kubernetes/community.
/lifecycle stale

fejta-bot on 9 Feb 2021

/remove-lifecycle stale

Ping

howardjohn on 9 Feb 2021

👍2

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-contributor-experience at kubernetes/community.
/lifecycle stale

fejta-bot on 10 May 2021

/remove-lifecycle stale

eddiezane on 13 May 2021

Was this page helpful?

0 / 5 - 0 ratings