kubernetes-helm

问题 The situation I have a kubernetes pod stuck in "Terminating" state that resists pod deletions NAME READY STATUS RESTARTS AGE ... funny-turtle-myservice-xxx-yyy 1/1 Terminating 1 11d ... Where funny-turtle is the name of the helm release that have since been deleted. What I have tried try to delete the pod. Output: pod "funny-turtle-myservice-xxx-yyy" deleted Outcome: it still shows up in the same state. - also tried with --force --grace-period=0 , same outcome with extra warning warning:

问题 Given 3 jobs (A,B,C) in 3 Helm charts, is it possible to run A and B jobs in parallel, then start job C as soon as both of them are finished? Think of a barrier, in which a bunch of stuff needs to be finished before moving on. Even if I put A and B charts as sub-charts for C chart, then all 3 are started in parallel. I already have an workaround for this: add an external check for A and B job finishing, then start C. Still, I would prefer a Helm-based solution, if it exists. 回答1: Kubernetes

问题 Using https://golang.org/pkg/text/template/, I sometimes need to use variables in the accessed path (for kubernetes deployments). I end up writing something like : {{ if (eq .Values.cluster "aws" }}{{ .Values.redis.aws.masterHost | quote }}{{else}}{{ .Values.redis.gcp.masterHost | quote }}{{end}} What I'd really like to write is pretty much {{ .Values.redis.{{.Values.cluster}}.masterHost | quote }} , which doesn't compile. Is there a way to write something similar ? (so having a kind of

问题 I have a helm repository set up for my CI/CD pipeline, but the one thing I am having trouble with is helm's versioning system which is focused on a semantic versioning system as in x.x.x . I want to be able to specify tags like "staging", "latest", and "production", and although I am able to successfully upload charts with string versions NAME CHART VERSION APP VERSION chartmuseum/myrchart latest 1.0 Any attempt to actually access the chart fails, such as helm inspect chartmuseum/mychart -

问题 I would like to run some kubectl commands to verify the cluster post install of Helm charts. I could not find any documentation around this. In Helm, theres the concept of showing notes as part of NOTES.txt but doesnt look like you can run any commands at that stage. Is this currently impossible to do with Helm ? 回答1: You can define a job that is executed at a certain point in the lifecycle during helm install . The list of available hooks also contains a post-install hook you are probably

问题 This is values.yaml file. It contains the following and when I am trying to get it into _helper.tpl im getting Helm template failed. Error: render error in "windows/templates/ingresses/windows.yaml": template: windows/templates/_helpers.tpl:38:18: executing "windows.certificate" at <.Values.ingress.enab...>: can't evaluate field ingress in type interface {} : exit status 1 values.yaml ingress: enabled: true tls: true certificate: '' issuer: name: letsencrypt-staging hosts: windows: - name: ''

问题 I have kubernetes Cluster v1.10 over centos 7 , bare-metal helm version Client: &version.Version{SemVer:"v2.11.0-rc.3", GitCommit:"28d295be2a94115b786ee277dffcc2b5483bde47", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.11.0-rc.3", GitCommit:"28d295be2a94115b786ee277dffcc2b5483bde47", GitTreeState:"clean"} I am trying to install nginx using helm helm install stable/nginx-ingress --name nginx It returns Error: release nginx failed: clusterroles.rbac.authorization.k8s.io "nginx

问题 I successfully deployed Kafka to Kubernetes on local Docker (gcp & minikube) using Yolean/kubernetes-kafka & Helm chart and tested topic production successfully from within the cluster using this python script: #!/usr/bin/env python from kafka import KafkaConsumer, KafkaProducer KAFKA_TOPIC = 'demo' # KAFKA_BROKERS = 'localhost:32400' # see step 1 # from inside the cluster in a different namespace # KAFKA_BROKERS = 'bootstrap.kafka.svc.cluster.local:9092' KAFKA_BROKERS = 'kafka.kafka.svc

问题 I have a kubernetes cluster built using kubespray and imported to Rancher. The nodes are configured with CentOS Linux 7 3.10.0-957.12.1.el7.x86_64 Docker version : 18.9.5 Kubelet version : v1.14.1 Tiller version : v2.14.1 ( got this version from the tiller pod's image gcr.io/kubernetes-helm/tiller:v2.14.1 ) All the tiller resources are working fine: $ kubectl get all -n kube-system | findstr tiller pod/tiller-deploy-57ff77d846-frtb7 1/1 Running 0 12d service/tiller-deploy ClusterIP 10.233.49

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed last year . I am trying to loop for a count in a kubernetes helm chart like this: reaction.mongo_url_big: mongodb://{{ for $mongocount := 0; $mongocount < {{ .Values.mongodbReplicantCount }}; $mongocount++ }}{{ .Values.mongodbReleaseName }}-mongodb-replicaset-{{ $mongocount }}:{{ .Values