[Bug] Cost analyzer pod in CrashLoopBackOff after enabling the readonly feature #3433
Open
2 tasks done
Labels
bug
Something isn't working
Kubecost Helm Chart Version
2.2.5
Kubernetes Version
1.27
Kubernetes Platform
AKS
Description
I installed kubecost using the helm chart, enabling the readonly feature, and the aggregator container in the kubecost-cost-analyzer pod started failing leaving the pod in CrashLoopBackOff status making kubecost UI inaccessible.
Steps to reproduce
helm install kubecost cost-analyzer \ --repo https://kubecost.github.io/cost-analyzer/ \ --namespace kubecost --create-namespace \ --set kubecostToken="bWFyaW9qdWFyZXpjQGdtYWlsLmNvbQ==xm343yadf98" \ --set readonly=true
kubectl -n kubecost logs kubecost-cost-analyzer-5dcbc54c48-hd2s7 -c aggregator -f
Error: listen tcp :9004: bind: address already in use
Expected behavior
It is expected to kubecost run as usual but disabling updates to kubecost from the frontend UI and via POST request as described in the values.yaml file
cost-analyzer-helm-chart/cost-analyzer/values.yaml
Line 3156 in c11a9bb
Impact
No response
Screenshots
No response
Logs
Slack discussion
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: