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

Show Workload Status on Home Page #644

Merged
merged 1 commit into from
May 10, 2024

Conversation

ricoberger
Copy link
Member

It is now possible to show the status for Pods, Deployments, StatefulSets, DaemonSets and Jobs on the home page. This feature can be enabled seperatly for each workload in the home page settings.

When enabled we display for each workload the total number of resources and the count for each resource status. When a user click on the workload, he can directly view all the resources with the selected status.

For this the ResourcesList widget now contains a status parameter, which is set to the user selected status to filter the resources accordingly.

It is now possible to show the status for Pods, Deployments,
StatefulSets, DaemonSets and Jobs on the home page. This feature can be
enabled seperatly for each workload in the home page settings.

When enabled we display for each workload the total number of resources
and the count for each resource status. When a user click on the
workload, he can directly view all the resources with the selected
status.

For this the `ResourcesList` widget now contains a `status` parameter,
which is set to the user selected status to filter the resources
accordingly.
@ricoberger ricoberger added the changelog: added A new feature was added label May 10, 2024
@ricoberger ricoberger merged commit 8e4693c into main May 10, 2024
2 checks passed
@ricoberger ricoberger deleted the show-workload-status-on-home-page branch May 10, 2024 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: added A new feature was added
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant