Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-5747

Update permissions of Tempo PersistentVolume

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhosdt-3.9
    • None
    • None
    • None
    • Update permissions of Tempo PersistentVolume
    • Future Sustainability
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      Out of the box, users of the Tempo operator upstream run into permission issues on DigitalOcean and AWS:
      https://github.com/grafana/tempo-operator/issues/1240
      https://github.com/grafana/tempo-operator/issues/996
      https://docs.digitalocean.com/products/kubernetes/how-to/add-volumes/#setting-permissions-on-volumes

      The main problem is that the Tempo process runs as user 10001, but the filesystem in the PV is owned by root:root.

      To fix this, we can set fsGroup: 10001 by default, which chown's the PV to the right user.

       

       

      The fix should not break any existing installations. 

              rvargasp@redhat.com Ruben Vargas Palma
              agerstma@redhat.com Andreas Gerstmayr
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: