kubernetes-helm

How to set a different namespace for child helm charts?

由 我的未来我决定 提交于 2019-12-01 03:24:36
问题 When you install a chart with a child chart that doesn't specify a namespace, Helm will use the one specified on command line via --namespace . Is it possible to override this flag for a specific child chart? For example if I have chart A which depends on chart B and I specify --namespace foo , I want to be able to customize the resources of chart B to be installed into some other namespace bar instead of foo . 回答1: Update 2: Helm 3 added support for multi namespaces https://github.com/helm

How do I use json variables in a yaml file (Helm)

由 二次信任 提交于 2019-12-01 03:08:37
问题 I have a HELM values file which looks like so: service: environment: dev spring_application_json: >- { "spring" : { "boot" : { "admin" : { "client" : { "enabled" : "false", "url" : "http://website1", "instance" : { "service-base-url" : "http://website2", "management-base-url" : "http://website3" } } } } } } And a corresponding template file which grabs this value and inserts it as an environment variable to a container. spec: replicas: {{ .Values.replicaCount }} template: spec:

Unable to install kubernetes charts on specified namespace

由 随声附和 提交于 2019-11-30 07:17:00
I have installed a cluster on Google Kubernetes Engine. And then, I created namespace "staging" $ kubectl get namespaces default Active 26m kube-public Active 26m kube-system Active 26m staging Active 20m Then, I switched to operate in the staging namespace $ kubectl config use-context staging $ kubectl config current-context staging And then, I installed postgresql using helm on staging namespace helm install --name staging stable/postgresql But I got: Error: release staging failed: namespaces "staging" is forbidden: User "system:serviceaccount:kube-system:default" cannot get namespaces in

Kubernetes pod unable to connect to rabbit mq instance running locally

由 我的未来我决定 提交于 2019-11-29 17:09:59
I am moving my application from docker to kubernetes \ helm - and so far I have been successful except for setting up incoming \ outgoing connections. One particular issue I am facing is that I am unable to connect to the rabbitmq instance running locally on my machine on another docker container. app-deployment.yaml: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: jks labels: app: myapp spec: replicas: 1 template: metadata: labels: app: myapp spec: imagePullSecrets: - name: ivsecret containers: - env: - name: JOBQUEUE value: jks_jobqueue - name: PORT value: "80" image: repo

Helm delete all releases

由 ￣綄美尐妖づ 提交于 2019-11-29 16:24:48
问题 I'm trying find a way to delete all deployed releases in Helm. It appears that Helm does not support deleting all releases, with --all or otherwise. Would there be another way to delete all Helm releases in one command? 回答1: To delete all Helm releases with a single command, you can use some good old bash. Just pipe the output of helm ls --short to xargs , and run helm delete for each release. helm ls --all --short | xargs -L1 helm delete Adding --purge will delete the charts as well, as per

How to reference a value defined in a template in a sub-chart in helm for kubernetes?

由 故事扮演 提交于 2019-11-29 11:09:12
问题 I'm starting to write helm charts for our services. There are two things I'm not sure how they are supposed to work or what to do with them. First: the release name. When installing a chart, you specify a name which helm uses to create a release. This release name is often referenced within a chart to properly isolate chart installs from each other? For example the postgres chart contains: {{- define "postgresql.fullname" -}} {{- $name := default .Chart.Name .Values.nameOverride -}} {{-

Unable to install kubernetes charts on specified namespace

由 冷暖自知 提交于 2019-11-29 09:22:27
问题 I have installed a cluster on Google Kubernetes Engine. And then, I created namespace "staging" $ kubectl get namespaces default Active 26m kube-public Active 26m kube-system Active 26m staging Active 20m Then, I switched to operate in the staging namespace $ kubectl config use-context staging $ kubectl config current-context staging And then, I installed postgresql using helm on staging namespace helm install --name staging stable/postgresql But I got: Error: release staging failed:

Error: error installing: the server could not find the requested resource HELM Kubenetes

由 两盒软妹~` 提交于 2019-11-27 03:35:58
问题 What I Did: I installed Helm with curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get | bash helm init --history-max 200 Getting an error: $HELM_HOME has been configured at /root/.helm. Error: error installing: the server could not find the requested resource what does that error mean? How should I install Helm and tiller? Ubuntu version: 18.04 Kubernetes version: 1.16 Helm version: helm version Client: &version.Version{SemVer:"v2.14.3", GitCommit:
订阅 kubernetes-helm