helm-charts | Development repo for helm charts | Continuous Deployment library

Installing grafana using helm charts, the deployment goes well and the grafana ui is up, needed to add an existence persistence volume, ran the below cmd:

I searched for a solution to have confluentic-kafka work with ingress, and I reached this PR that did such implementation, but this PR isn't accepted (yet - the repository owner dropped and the repo doesn't exist any more).

So, I tried to implement something very simple as a proof of concept using as a reference this manual.

Currently I have ingress enabled:

I am working with https://github.com/prometheus-community/helm-charts and am running into some issues with a couple of regex queries are a part of our basic yaml deployments. The issue I'm having is specifically with the Node exporter part of the prometheus chart. I have configured this:

So I installed kube-prometheus-stack from this tutorial:

I have a react SPA (Single Page Application) and want to deploy it to a Kubernetes environment. For the sake of keeping it simple, assume the SPA is stand alone.

I've been told Bitnami's repo for Helm Charts are a good place to start to solve this problem. So my question is what Bitnami chart should I use to deploy a react SPA to a Kubernetes cluster? And where can I find the steps explained?

The desired solution should be a Helm Chart that serves up static content. Typically app.js and index.html page, and other static content. And lets me specify the sub-directory to use as the contents of the website. In react, the build subdirectory holds the website.

What I currently do is described below. I'm starting from a new app created by create-react-app so that others could follow along and do this if needed to helm answer the question. This assumes you have Docker, Kubernetes and helm installed (as well as node and npm for React).

The following commands do the following:

1. Create a new React application
2. Create a docker container for it.
3. Build and test the SPA running in a local docker image .
4. Create a helm chart to deploy the image to K8S.
5. Configure the helm chart so it uses the docker image created in step 3.
6. Using the helm CLI deploy the SPA app to the k8s cluster.
7. Test the SPA running in k8s cluster.

I have installed kube-prometheus-stack as a dependency in my helm chart on a local Docker for Mac Kubernetes cluster v1.19.7.

The myrelease-name-prometheus-node-exporter service is failing with errors received from the node-exporter daemonset after installation of the helm chart for kube-prometheus-stack is installed. This is installed in a Docker Desktop for Mac Kubernetes Cluster environment.

release-name-prometheus-node-exporter daemonset error log

I am trying to deploy to the Azure Kubernetes cluster using Helm charts. While trying to execute following command:

helm install --namespace custom-namspace my-project ./my-project

I am getting following error:

I have installed kube-prometheus-stack as a dependency in my helm chart on a local docker for Mac Kubernetes cluster v1.19.7. I can view the default prometheus targets provided by the kube-prometheus-stack.

I have a python flask service that provides metrics which I can view successfully in the kubernetes cluster using kubectl port forward.

However, I am unable to get these metrics displayed on the prometheus targets web interface.

The kube-prometheus-stack documentation states that Prometheus.io/scrape does not support annotation-based discovery of services. Instead the the reader is referred to the concept of ServiceMonitors and PodMonitors.

So, I have configured my service as follows:

I've code to deploy a helm chart using pulumi kubernetes. I would like to patch the StatefulSet (change serviceAccountName) after deploying the chart. Chart doesn't come with an option to specify service account for StatefulSet.

here's my code