Channels
#neuvector-security
Title
# neuvector-security
f
full-lawyer-94872
03/07/2023, 11:27 PMScreenshot 2023-03-08 at 04.54.56.png
q
quaint-candle-18606
03/08/2023, 3:10 PMwhat version of Neuvector?
f
full-lawyer-94872
03/08/2023, 3:49 PMits, 5.1.0
q
quaint-candle-18606
03/08/2023, 4:49 PMwould you mind rolling to 5.1.1 to see if things look better?
it’s squishes several annoyances (not sure if this is one of them off the top of my head, but 5.1.1 is worth the ~2 minutes of upgrade, IMO 😉 )
f
full-lawyer-94872
03/08/2023, 5:09 PMYep for sure, already got work on it actually 🙂 Just after posting here, I went through the new release changes today and found out that memory issue was one of them + it also fixes multiple UI issues (I too came across a few) / similar network issues and etc.
It will take way more than 2 mins though 😅 as automations are still on a baking-state and we do have multiple clusters + due to some resource onboarding practices like of the images being used and the charts.
q
quaint-candle-18606
03/08/2023, 5:14 PMYou’re slowed down by doing things correctly? crazytalk! 😂
f
full-lawyer-94872
03/08/2023, 5:15 PMExactly 😄
But once the automations are in-place, things will be more easier
q
quaint-candle-18606
03/08/2023, 5:16 PMa lot of underling architecture was changed in 5.1.0… and more bugs than usual squeezed through. 🤦 i wouldn’t even spend a lot of time testing with it until you’re looking at 5.1.1
f
full-lawyer-94872
03/08/2023, 5:19 PM+1
@quaint-candle-18606 Updated to 5.1.1 and a lot more stable than 5.1.0 as it seems 🙂
Even the controller mem. usages have gone down from ~2.6 Gig to ~700 MBs
though I do have a concern on the detections for K8s api server connections which I will add as a new question to the main thread.
5 Views