Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't set security context when on OpenShift #521

Merged
merged 3 commits into from
May 25, 2021
Merged

Don't set security context when on OpenShift #521

merged 3 commits into from
May 25, 2021

Commits on May 21, 2021

  1. Don't set security context when on OpenShift 

    * Envoy container should not have security context set when on OpenShift
  and when tproxy is disabled because we want to let OpenShift set a random
  user/group. When tproxy is enabled though, we need to still set it on OpenShift
  because we require Envoy to have a specific user for the traffic redirection to work.
* init-copy-container doesn't need to have security context set whenever running on OpenShift
  (regardless of whether tproxy is enabled or not) so that OpenShift can set its own random user/group.
    @ishustava
    ishustava committed May 21, 2021
    Configuration menu
    Copy the full SHA
    74e03e7 View commit details
    Browse the repository at this point in the history

  2. Code review comments

    @ishustava
    ishustava committed May 21, 2021
    Configuration menu
    Copy the full SHA
    fd4dd7d View commit details
    Browse the repository at this point in the history

  3. Update changelog

    @ishustava
    ishustava committed May 21, 2021
    Configuration menu
    Copy the full SHA
    6f5742e View commit details
    Browse the repository at this point in the history