You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that the Alertmanager pod keeps crashing (status is CrashLoopBackOff). I have deployed a debug pod and mounted the same volumes as Alertmanager in order to inspect the config file, and it looks like my user-supplied values are being overridden with the default values. I have also attached this config file. actual-pod-config.txt
Running the Helm upgrade command with the --debug flag shows the final computed configuration values. helm-debug.txt
Problem Details
The issue I am facing is that no matter what I do, I cannot seem to change the default Alertmanager storage value from s3 to local filesystem.
Greetings,
I am trying to run the Alertmanager pod with two options different from the default configuration:
I am really new to Kubernetes (K8s) and Cortex and haven’t worked with either of them before today.
I have tried to use some custom options using the following command:
I’ve attached the
cortex-values.yaml
file.cortex-values.txt
The problem is that the Alertmanager pod keeps crashing (status is CrashLoopBackOff). I have deployed a debug pod and mounted the same volumes as Alertmanager in order to inspect the config file, and it looks like my user-supplied values are being overridden with the default values. I have also attached this config file.
actual-pod-config.txt
Running the Helm upgrade command with the
--debug
flag shows the final computed configuration values.helm-debug.txt
Problem Details
The issue I am facing is that no matter what I do, I cannot seem to change the default Alertmanager storage value from s3 to local filesystem.
The output of the command:
kubectl-logs.txt
indicates that the reason for the pod's failure is an error trying to connect to an S3 endpoint. I have also attached this log output here.
Questions
Thanks!
The text was updated successfully, but these errors were encountered: