Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-2929 Fix the upstream E2E Tests from the OTEL Collector to work in OpenShift
  3. TRACING-2942

instrumentation-language OTEL Upstream tests fail in OpenShift due the security context of the business applications

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • OpenTelemetry, QE
    • None
    • False
    • None
    • False
    • Tracing Sprint # 229, Tracing Sprint # 230, Tracing Sprint # 231, Tracing Sprint # 232, Tracing Sprint # 233

      Some E2E tests deploy a business application to test the autoinstrumentation. That application cannot be deployed in OpenShift due to security context. This warning is shown when the deployment is created:

      
Warning: would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (containers "myapp", "myrabbit" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (containers "myapp", "myrabbit" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or containers "myapp", "myrabbit" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers "myapp", "myrabbit" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

      Affected E2E tests:

      • instrumentation-python
      • instrumentation-dotnet
      • instrumentation-java
      • instrumentation-nodejs
      • instrumentation-java-other-ns

              rhn-support-iblancas Israel Blancas Alvarez
              rhn-support-iblancas Israel Blancas Alvarez
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: