search

baselime / helm-charts

Helm Charts for Baselime
MIT License
2 stars 0 forks source link

Kubernetes Helm chart not working #1

Open Ismaaa opened 7 months ago

Ismaaa commented 7 months ago

The guide for Kubernetes is not updated and the commands don't work as expected

Guide: https://baselime.io/docs/sending-data/platforms/kubernetes/

Output:

➜  ~ helm repo add baselime-logs-exporter https://github.com/baselime/helm-charts

Error: repository name (baselime-logs-exporter) already exists, please specify a different name
➜  ~
Lastin commented 7 months ago

Hi @Ismaaa, thanks for reporting! It should now be sorted, just updating the docs to reflect the changes I've changed the url to https://baselime.github.io/helm-charts and the chart reference to baselime-logs-exporter/baselime-logs-exporter

So basically this:

helm repo add baselime-logs-exporter https://baselime.github.io/helm-charts
helm repo update
helm install baselime-logs-exporter baselime-logs-exporter/baselime-logs-exporter --values custom-values.yaml

Let me know if you run into any issues :wink:

Ismaaa commented 7 months ago

Thanks for taking a look at it @Lastin ! It indeed works now, now there's something on the chart that's not working as expected. I don't have this chart installed yet but it's throwing a very strange error.

helm install baselime-logs-exporter baselime-logs-exporter/baselime-logs-exporter -f ./values.yml --namespace=monitoring

Error: INSTALLATION FAILED: 1 error occurred:
    * serviceaccounts "baselime-metadata-collector" already exists

But then this command does not show any result:

kubectl get serviceaccounts --namespace monitoring | grep baselime

I even tried uninstalling with this:

helm uninstall baselime-logs-exporter --namespace monitoring

But still getting the same error

Lastin commented 6 months ago

Hi @Ismaaa. Apologies for late reply. Could you check if the service account was created in "default" namespace? Try running kubectl get serviceaccounts/baselime-metadata-collector -o yaml it should print namespace where it has been created.

Ismaaa commented 6 months ago

Hey @Lastin !

I don't have it installed, and this is the output:

kubectl get serviceaccounts/baselime-metadata-collector -o yaml
Error from server (NotFound): serviceaccounts "baselime-metadata-collector" not found

And same for the monitoring namespace

kubectl get serviceaccounts/baselime-metadata-collector -o yaml -n monitoring
Error from server (NotFound): serviceaccounts "baselime-metadata-collector" not found
Lastin commented 6 months ago

Can you try with --all-namespaces flag? Alternatively you should be able to overwrite the service account name by declaring this in your values.yaml file.

serviceAccount:
  name: baselime-service-account-2
Ismaaa commented 6 months ago

Got the same result with the flag

kubectl get serviceaccounts/baselime-metadata-collector -o yaml --all-namespaces
error: a resource cannot be retrieved by name across all namespaces
ricktg commented 3 days ago

The file charts/baselime-logs-exporter/templates/fluentbit-serviceaccount.yaml already creates the service account with same name. Maybe that is not intended?