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

How to override startup args for prometheus server #2454

Open
ForcemCS opened this issue Jul 6, 2024 · 1 comment
Open

How to override startup args for prometheus server #2454

ForcemCS opened this issue Jul 6, 2024 · 1 comment

Comments

@ForcemCS
Copy link

ForcemCS commented Jul 6, 2024

I'm getting into prometheus, and I'm currently having problems.how to override startup args for prometheus server
I am deploying prometheus using kube-prometheus-satck, how do I override the value of --storage.tsdb.path=/prometheus to --storage.tsdb.path=/prometheus/prometheus-db, I I tried the following VALUES. yaml modification, but when helm upgrade is executed, there are two configurations in the startup parameters, one for prometheus and one for prometheus-db

prometheus:
  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.class: nginx
    hosts:
    - prom.threshold.com
    tls:
    - hosts:
      - prom.threshold.com
      secretName: prom-threshold-com
  prometheusSpec:
    additionalArgs:
    #- name: 'storage.tsdb.retention.time=15d'
    - name: 'storage.tsdb.path=/prometheus/prometheus-db'
    - name: 'storage.tsdb.max-block-duration=2h'
    - name: 'storage.tsdb.min-block-duration=2h'
    - name: 'web.enable-admin-api'
    affinity:
      nodeAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 1
            preference:
              matchExpressions:
                - key: preferred
                  operator: In
                  values:
                    - prometheus
    storageSpec:
      volumeClaimTemplate:
        spec:
          storageClassName: local-prom-stack
Copy link

github-actions bot commented Sep 5, 2024

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant