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.

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

Ownership of file not changed after the upgrade from 2.4.1 to 2.6.0 #4290

Open
snyaik opened this issue Nov 6, 2024 · 1 comment
Open

Ownership of file not changed after the upgrade from 2.4.1 to 2.6.0 #4290

snyaik opened this issue Nov 6, 2024 · 1 comment

Comments

@snyaik
Copy link

snyaik commented Nov 6, 2024

Hi All,

I have recently tried upgrading the tempo distributed from 2.4.1 to 2.6.
One of the breaking change is the change in the ownership of the directory in var/tempo to user and group tempo.

After the upgrade I can see the ownership is only for the group.
I in the helm values file, I have added the securityContext and podSecurityContext.
Snippet of the config is mentioned below.
Also, just adding the securityContext did not update the ownership.
Please advise if there is anything else I have missed for the update.
I have followed the discussion on PR: #2265

tempo:
    image:
      # -- The Docker registry
      registry: docker.io
      # -- Optional list of imagePullSecrets. Overrides `global.image.pullSecrets`
      pullSecrets: []
      # -- Docker image repository
      repository: grafana/tempo
      # -- Overrides the image tag whose default is the chart's appVersion
      tag: null
      pullPolicy: IfNotPresent
    readinessProbe:
      httpGet:
        path: /ready
        port: http-metrics
      initialDelaySeconds: 30
      timeoutSeconds: 1
    # -- Global labels for all tempo pods
    podLabels: {}
    # -- Common annotations for all pods
    podAnnotations: {}
    # -- SecurityContext holds container-level security attributes and common container settings
    securityContext:
      runAsUser: 10001
      runAsGroup: 10001
      fsGroup: 10001
      runAsNonRoot: true
      allowPrivilegeEscalation: false
      capabilities:
        drop:
          - ALL
      readOnlyRootFilesystem: true
    # -- podSecurityContext holds pod-level security attributes and common container settings
    podSecurityContext:
      fsGroup: 10001
      runAsGroup: 10001
      runAsUser: 10001
@mapno
Copy link
Member

mapno commented Nov 15, 2024

Following this conversation, I believe you need to chown the folder manually. cc'ing @zalegrala as he has the most context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants