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
As part of Kubernetes' best practices, I'd like to set Security Context values in all the containers deployed on my infrastructure. As of now, the charts in weave-scope lack this capability.
ATM, the only value that get instantiated is the fsGroup:
@blame19 - makes sense. If you have time to submit a PR, we would welcome it. Otherwise, we will tackle this in the comings weeks as part of work we are planning for the 1.3 Release
As part of Kubernetes' best practices, I'd like to set Security Context values in all the containers deployed on my infrastructure. As of now, the charts in weave-scope lack this capability.
ATM, the only value that get instantiated is the fsGroup:
If we had something like
we could add a full scope of securityContext options to the containers.
The text was updated successfully, but these errors were encountered: