kubernetes-helm

问题 I am working on an application which deploys helm charts to kubernetes cluster on user's demand. Helm charts are stored in private repo on github. The scenario is whenever user request an application deployment the system fetches chart from git repo build it and deploy it on the cluster.Helm does not provide REST api (as it uses gRPC protocol to talk to tiller server) and helm-cli is not the option to use in this scenario so my question is Is their any way to call tiller services without

问题 I can't seem to find any clear information on this anywhere, but is it possible in a Helm chart to require a third party, such as stable/jenkins , and specify configuration values? All the examples I see are for running the helm install command directly but I would like to be able to configure it as part of my application. 回答1: In answer, @desaintmartin referred me to these documents in Slack: Subcharts and Globals Requirements Helm Dependencies This led me to find the specific part I was

问题 I can't seem to find any clear information on this anywhere, but is it possible in a Helm chart to require a third party, such as stable/jenkins , and specify configuration values? All the examples I see are for running the helm install command directly but I would like to be able to configure it as part of my application. 回答1: In answer, @desaintmartin referred me to these documents in Slack: Subcharts and Globals Requirements Helm Dependencies This led me to find the specific part I was

问题 Can I have multiple values.yaml files in a Helm chart? Something like mychart/templates/internalValues.yaml , mychart/templates/customSettings.yaml , etc? Accessing properties in a values.yaml file can be done by {{ .Values.property1 }} . How would I reference the properties in these custom values.yaml files? 回答1: Helm by default will only use the values.yaml file in the root directory of your chart. You can ask it to load additional values files when you install. For instance, if you have

问题 Can I have multiple values.yaml files in a Helm chart? Something like mychart/templates/internalValues.yaml , mychart/templates/customSettings.yaml , etc? Accessing properties in a values.yaml file can be done by {{ .Values.property1 }} . How would I reference the properties in these custom values.yaml files? 回答1: Helm by default will only use the values.yaml file in the root directory of your chart. You can ask it to load additional values files when you install. For instance, if you have

问题 I've recently asked a question about how to structure multiple applications which should be bundled together and am thinking of going down a route of having each separate application have it's own Helm chart and own ingress controller. This would allow for CI/CD to update each component easily without affecting the rest. I was also thinking about using a "Umbrella" chart to specify versions of the other charts when it comes to actual releases and keep that in another repo. However, when using

问题 I've recently asked a question about how to structure multiple applications which should be bundled together and am thinking of going down a route of having each separate application have it's own Helm chart and own ingress controller. This would allow for CI/CD to update each component easily without affecting the rest. I was also thinking about using a "Umbrella" chart to specify versions of the other charts when it comes to actual releases and keep that in another repo. However, when using

问题 Please! Is it possible to squash multiple helm templates into one and then refer to it as a one-liner in a deployment file? EG: {{- define "foo.deploy" -}} value: {{- include "foo.1" . | nindent 6 }} {{- include "foo.2" . | nindent 6 }} {{- include "foo.3" . | nindent 6 }} And then do an {{- include "foo.deploy" . }} in a separate deployment file. Which should then contain foo.1, foo.2 and foo.3, and their respective definitions. As opposed to literally writing out all three different

问题 I'm using helm charts to deploy several REST services to Microsoft Azure. Some of these services communicate with each other and to some databases. After the deployment I want to test if "everything" works as expected. To be more precise, I want to send some HTTP requests to one of the services and check if the response makes sense. In automated tests of course. I saw that it's possible to run basic commands after the deployment using "helm test", but this is not exactly what I need. In some

问题 i.e. from name: {{ .Chart.Name }}-{{ .Values.module5678.name }}-pod below # deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: labels: app: {{ template "project1234.name" . }} chart: {{ template "project1234.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} name: {{ template "project1234.module5678.fullname" . }} spec: replicas: {{ .Values.replicaCount }} selector: matchLabels: app: {{ template "project1234.name" . }} template: metadata: labels: app: {{