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
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
Hi, this request is similar to #904; however, in this case we'd like to have the container-scoped securityContext configurable, and passed to the spawned pods.
This would allow us to set capabilities for the spawned containers (such as NET_ADMIN), which would in turn enable us to run tc/netem to induce impaired networking conditions in the client browser test environment.
I think its something to investigate implementing, the hub may not always need/want the same level of permissions than that of the nodes, similar to that of the kubernetes service account.
Hi, this request is similar to #904; however, in this case we'd like to have the container-scoped securityContext configurable, and passed to the spawned pods.
This would allow us to set capabilities for the spawned containers (such as NET_ADMIN), which would in turn enable us to run tc/netem to induce impaired networking conditions in the client browser test environment.
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#securitycontext-v1-core
Please let me know if you'd like further elaboration.
Thanks,
Martin
The text was updated successfully, but these errors were encountered: