You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Renamed existing securityContext to podSecurityContext. If you configured a securityContext before to rename the property. E.g. juiceBalancer.securityContext to juiceBalancer.podSecurityContext.
🚀 Features
Updated to JuiceShop v15.2.0 as default JuiceShop version. This version contains a new ScoreBoard and new Blockchainy Challenges. Also brings performance improvements for both the server (15-20% less CPU and Memory usage) which should help reducing costs for MultiJuicer setups :)
Added option to configure kubernetes securityContexts on the container level via new containerSecurityContext helm value. Thanks @jonasbg 🙌
Both podSecurityContext & containerSecurityContext are now configured with sensible and locked down defaults for all components. See values.yaml for the new default values. Thanks @jonasbg for providing the default
values 🙌
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What's Changed
🚨 Breaking
securityContext
topodSecurityContext
. If you configured asecurityContext
before to rename the property. E.g.juiceBalancer.securityContext
tojuiceBalancer.podSecurityContext
.🚀 Features
securityContexts
on the container level via newcontainerSecurityContext
helm value. Thanks @jonasbg 🙌podSecurityContext
&containerSecurityContext
are now configured with sensible and locked down defaults for all components. See values.yaml for the new default values. Thanks @jonasbg for providing the defaultvalues 🙌
📚 Documentation
🔧 Maintenance
New Contributors
Full Changelog: v6.1.0...7.0.0
This discussion was created from the release v7.0.0.
Beta Was this translation helpful? Give feedback.
All reactions