Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRD does not show the output like kubectl #7633

Open
anannaya opened this issue Feb 26, 2023 · 5 comments · May be fixed by #8583
Open

CRD does not show the output like kubectl #7633

anannaya opened this issue Feb 26, 2023 · 5 comments · May be fixed by #8583
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@anannaya
Copy link

anannaya commented Feb 26, 2023

What happened?

We use flinkApplication operator , which shows the output status using kubectl like this

k get flinkApplication -A
NAMESPACE        NAME                                           PHASE           CLUSTER HEALTH   JOB HEALTH   JOB RESTARTS   AGE
agentproc        agent-snapshot-metrics                         Running         Green            Green        2              4d10h
agentproc        agent-statistics-metric-processor              Running         Green            Green        1              11d
agentproc        agent-summary-processor                        Running         Green            Green        1              4d10h
agentproc        site-snapshot-metrics                          Running         Green            Green        2              4d10h
agentproc        team-snapshot-metrics                          Running         Yellow           Yellow       4              430d
agentproc        usage-metric-processor                         Running         Green            Green        2              73d
agentstorage     raw-data-agent-storage-agent-activity          Running         Green            Green        3              4d10h
agentstorage     raw-data-agent-storage-agent-error             Running         Yellow           Yellow       11             533d
agentstorage     raw-data-agent-storage-agent-event             Running         Yellow           Yellow       11             533d
agentstorage     raw-data-agent-storage-agent-statistics        Running         Yellow           Yellow       11             533d
agentstorage     refined-data-agent-storage-agent-state         Running         Green            Green        1              21d
billing          agent-pstn-snapshot-metrics                                                                                 2d12h

But in a kubernetes dashboad does not shows these information , Is there any way to customize in UI?
image

What did you expect to happen?

Does not show the proper output in UI,

How can we reproduce it (as minimally and precisely as possible)?

Any CRD can be tested .

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

v2.7.0

Kubernetes version

1.23

Dev environment

No response

@anannaya anannaya added the kind/bug Categorizes issue or PR as related to a bug. label Feb 26, 2023
@floreks
Copy link
Member

floreks commented Feb 26, 2023

This is unfortunately not supported right now. We do not have any logic to read custom print columns as described in the k8s docs. It would be an enhancement.

https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#additional-printer-columns

@floreks floreks added kind/feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed kind/bug Categorizes issue or PR as related to a bug. labels Feb 26, 2023
@anannaya
Copy link
Author

@floreks Thanks for responding .

@ashutosh887
Copy link

@floreks I would like to work on this

@anannaya
Copy link
Author

@ashutosh887 i can test and confirm.once the changes are ready

@RafikFarhad
Copy link
Contributor

@maciaszczykm I would like to work on this if @ashutosh887 is no longer interested.
Thanks.

@RafikFarhad RafikFarhad linked a pull request Dec 31, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants