helmchart | Helm chart for kubernetes deployments | Continuous Deployment library

I'm deploying hazelcast on k8s using the helmchart on github currently on revision 5.3.2.

How would one go about running two clusters, say dev_cache and qa_cache in one helm deployment each with different members? Is that possible?

I see the fields

I want to get appVersion from chart.yaml file and compare with version which getting from project.csproj file.

So, I create three tasks that

1. version reader which getting version from project.csproj
2. file content to variable to get content from chart.yaml
3. powerscript shell that compare version and appVersion

file content to variable get all content. I only want to get appversion.

How to possible like this $env:helmchart_appVersion How can I get appVersion from chart.yaml ?

here my example.

$env:Project_Version is getting from Version Reader

$env:helmchart is getting from File content to variable

chart.yaml file :

I am using helm charts for deploying different services. I have parameterized my charts, so for every services I just pass new app name and it creates new service and related stuff.

All these services are residing in different namespace.

I have created ingress controller, which I want to use for all the services by just adding new rules for each service.

I tested deployment for one service, it worked successfully but when I am trying to deploy remaining services Its giving me error:

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.

We have recurring latencies in our Openshift cluster.

How can we (besides installing Istio - which is on the way) measure these latencies to get more information?

Is there some helmchart out there that exists for such a purpose?

Here is a result from our Gatling test:

I am trying to expose KAFKA in my Kubernetes setup for external usage using node port.

My Helmcharts kafka-service.yaml is as follows:

I am trying to install spinnaker on Kubernetes with Terraform using the following resource:

I am getting the below error while executing the helm chart.

Error: YAML parse error on helmcharts/templates/route.yaml: error converting YAML to JSON: yaml: line 25: could not find expected ':'

The chart works fine if I remove the multiline string "|-" from the Values.yaml file while referring the certificate to route.yaml. Since I remove "|-" the cert contents are not preserved with proper indentation while it's copied to route.yaml and the route fail to create.

I am trying to access the individual value from an array available in values.yaml file from my helmchart. My values.yaml file content