terraform-provider-helm VS helm-charts

seems like you can by passing in the path to a local folder https://github.com/hashicorp/terraform-provider-helm/issues/189

for some reason wasnt for the life of me able to find anything of value in global network. the closest one might be this: https://github.com/hashicorp/terraform-provider-helm/issues/425

When the helm provider is literally broken when trying to install istio onto a cluster

Helm installed on your machine. The Elastic modules will be installed using the official Elastic Helm repo. Although the repo is now read-only, it is still fully functional, and the community is expected to maintain it.

The Elastic Stack is our Swiss Army Knife on the cluster. The whole Elastic Stack has been installed in version 8.5.1 inside the cluster. We know it's not recommended to have stateful apps in Kubernetes, but we are in the early stage of our production.

Hi, I am looking to load the default dashboards that come pre-built in Kibana by setting up a Kibana endpoint in metricbeat configuration. The "setup.kibana" option is not really available in the official metricbeat helm charts as a setting (https://github.com/elastic/helm-charts/blob/main/metricbeat/values.yaml). The option to setup a kibana endpoint is only available in the regular metricbeat.yml file which we generally use in a VM based deployment. (https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-reference-yml.html).

apiVersion: networking.k8s.io/v1 kind: Ingress #https://kubernetes.io/docs/concepts/services-networking/ingress/ metadata: name: quickstart-es-http-ingress annotations: # nginx.ingress.kubernetes.io/rewrite-target: / #https://github.com/elastic/helm-charts/issues/779 https://stackoverflow.com/questions/68893838/ingress-for-eck-elasticsearch-not-working-502-gateway #kubernetes.io/ingress.class: nginx #think this is wrong for our class? kubernetes.io/tls-acme: "true" #nginx.ingress.kubernetes.io/proxy-ssl-secret: "resources/elastic-certificate-pem" #=> need to point to ES certificate pem. nginx.ingress.kubernetes.io/proxy-ssl-verify: "false" #=> must be false if you use elasticsearch-utils to generate CA. nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" #=> must be HTTPS <- this one fixed it. spec: ingressClassName: public rules: - http: paths: - path: / pathType: Prefix backend: service: name: quickstart-es-http port: number: 9200

Unfortunately the new security system introduced by ES 8.0 has produced problems with the official helm chart, so we cannot use the standard Okteto Chart deploy system. In this article we will see how deploy ES 8.x into kubernetes (k8s) using the Okteto Cloud as platform.

This might help you, you'd need to run this separately from the operator: https://github.com/elastic/helm-charts/blob/main/logstash/ Before embarking on a logstash journey you may want to check if beats (or agent) combined with Elasticsearch ingestion pipelines can meet your needs

We will deploy the Elasticsearch and Kibana using the official Helm charts which can be found here(Elasticsearch, Kibana). For installing via Helm you would need a helm binary on your path but installation of Helm is outside the scope of this post.

They have the repo with their helm charts published on github. Here's the values.yaml for elastic. The other apps (kibana, filebeat, etc) are in adjacent folders. The values you see in these files are the defaults.

Looks like they have recently changed node.roles https://github.com/elastic/helm-charts/pull/1186