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

Please render environment variables as a table #9474

Open
radarsh opened this issue Sep 17, 2024 · 3 comments · May be fixed by #9922
Open

Please render environment variables as a table #9474

radarsh opened this issue Sep 17, 2024 · 3 comments · May be fixed by #9922
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@radarsh
Copy link

radarsh commented Sep 17, 2024

What would you like to be added?

It would be far more readable to have container level environment variables displayed in tabular format instead of the current flow design and have options to sort, paginate, search etc like other tables on the dashboard.

Currently when we have a large number of environment variables:

image

Why is this needed?

Makes it much easier to read.

@radarsh radarsh added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 17, 2024
@maciaszczykm maciaszczykm added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Sep 19, 2024
@r-yabyab
Copy link
Contributor

r-yabyab commented Nov 5, 2024

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 3, 2025
@radarsh
Copy link
Author

radarsh commented Feb 3, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 3, 2025
@iamrajiv iamrajiv linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants