Closed keithhand closed 3 months ago
Thanks for reporting, @keithhand! Can you share example you've seen where this is true?
Sure! Any of the panels on this page are what I am talking about. The "orphaned-resources" panel was the targeted one, but the same idea would apply to all of them.
+1 , P1
I'll mark this with a product-triage for now - We can prioritize for 101 if need be!
I'm interested to learn more about specifics around where this doesn't apply? i.e. is it just a simple as they don't want to delete these resources?
I believe that's the case. From what I understand, there is a situation where a developer would deploy Kubecost and hand it off to a management team. When the management team asks about the orphaned resources, there is nothing they can do because of architectural constraints. So they want the information to reflect only savings for changes they can make.
That's helpful! We have a new guided savings experience in design. One concept related to that mode is the potential to archive / mark insights as not relevant. I feel like that pattern may be more appropriate here. Let me know if others feel differently.
@kwombach12 @Annalillie
I agree, having the option to hide insights that aren't relevant to the user would be very useful here. Guided savings aim to streamline the savings experience, so I think this is a great place for it to live. Along with the other guided features, this will add to the users ability to focus on the savings that are relevant to their unique situations.
Here are some mocks for variation. One for customizing savings insights within the guided savings experience as well as one for the savings main page. Users would have the ability to toggle the insights they find relevant.
@Annalillie -- Can this be Admin only ? Only Admin can enable disable ?
From a UI/UX perspective this could be achieved, however @dwbrown2 @kwombach12 would be able to give better insight to this proposal.
Thanks for this, Anna! My intuition is that we may want to drill deeper and enable hiding/archiving specific recommendations... i.e. does a user not want to see ANY orphaned resources suggestions or are some of the suggestions actually active resources and therefore these insights should be snoozed or archived.
+1 on make this Admin or Write only.
@dwbrown2 -- bump @keithhand , @Adam-Stack-PM
@wamak9 Thanks for the the bump. @kwombach12, As you are building out roadmaps wanted to get this on your radar for prioritization and consideration.
We're exploring a number of different approaches at this time!
is there an ETA on this ? @dwbrown2
bump +1
@wamak9 we have a product design doc in the works. We'll have it finalized in the next several weeks. Would you want to give input?!
yeah sure. bump
@kwombach12 can share more, this is now starting implementation this release
@dwbrown2 is correct! We will be adding the ability to hide/archive specific savings cards in 104. In future releases, we will enhance this further to provide the ability to hide specific savings recommendations.
Closing, stale. For any future enhancements or bugs which do not pertain specifically to the Helm chart, please log them in the features-bugs repo.
What problem are you trying to solve? Some available savings options might not be plausible depending on the user's architecture. This can lead to significant savings numbers that might never be achievable.
Describe the solution you'd like A way to hide specific panels on the savings page.
Describe alternatives you've considered Ignore the panels that aren't used
How would users interact with this feature? Helm configuration to set specific panels as disabled. Maybe something similar to:
┆Issue is synchronized with this Jira Task by Unito