So you guys jack up the subscription price, give us a new version of Lens without any community feedback or testing that many find substandard, and you’ve taken away the ability to use extensions (One of the big features I pay money to use), and you have a security center with no way to install the Trivy Operator to actually use. As far as I can see, there’s no way to manually scan an image either…
Not happy…
Hello there, thanks for reaching out to us.
We will definitely improve our communication channels to make sure next time no user is left out of the scope of our changes. However, we have been working with the community since March of the present year when we introduced the first Beta version of this update to collect feedback about the changes we were planning, and receive help testing them (Announcing Lens 2024 , What to Expect from Lens 2024 Early Access). Since then, hundreds of users have helped us shape the current state of the product
In regards to the support to Extensions, the team is working hard to bring them back in this newest version of Lens. Unfortunately, we required major architectural changes to improve the way extensions work and support newer/better features. If extensions are a key functionality you rely on, we recommend to downgrade the software until we announce they are back → Lens Subscription and Licensing FAQ - Lens Documentation
In regard to the Trivy Operator, if the notice to install it does not appear in the Security Center, it might be that your cluster has already CRs and CRDs related to Trivy that we used for its detection, so Lens “thinks” Trivy is already installed. Please follow the cleanup instructions mentioned at the end of this page Install Trivy Operator - Lens Documentation , specifically removing the CRDS kubectl get crds | grep "aquasecurity" | xargs kubectl delete crds, so you can get the notice back.
Thanks for the feedback provided, we value all users opinions to keep improving our Product
That’s awesome for people who have been around since March and earlier.
I discovered Lens last month, loved it, and instantly grabbed a subscription, not knowing that any of this architectural change was in progress.
Improving a product is one thing. But removing paid-for features with the promise of adding them back in at some point in the future is just a horrible experience for any customer of any software product.
Yes, Trivy was previously installed on the cluster and removed. So those crds were still present even though the pods and namespace were not. A simple button in the cluster settings that would install the operator fresh no matter the state of the cluster would be a much better user experience. The logic already seems to be there with the somewhat flaky lens-metrics switches?