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: Immediate deletion does not wait for confirmation that the running resource has been terminated. The

I run helm upgrade --install to modify the state of my kubernetes cluster and I sometimes get an error like this: 22:24:34 StdErr: E0126 17:24:28.472048 48084 portforward.go:178] lost connection to pod 22:24:34 Error: UPGRADE FAILED: transport is closing It seems that I am not the only one, and it seems to happen with many different helm commands. All of these github issues have descriptions or comments mentioning "lost connection to pod" or "transport is closing" errors (usually both): https://github.com/kubernetes/helm/issues/1183 https://github.com/kubernetes/helm/issues/2003 https://github

I have a private Docker repo with bunch of images. I am using Helm to deploy them to a Kubernetes cluster. Helm values.yaml contains the repository credentials: image: repository: <repo> tag: <version tag> pullPolicy: IfNotPresent imageCredentials: registry: <repo> username: <username> password: <pw> After doing the helm installation helm install myhelmchart --values values.yaml --version the pod's status is Init:ErrImagePull. kubectl describe pods gives this error: Failed to pull image "image:tag": rpc error: code = Unknown desc = Error response from daemon: Get [image]/manifests/[version]:

Using Helm templates, I'm trying to generate a list of server names based on a number in values.yaml. The dot for this template is set to the number (its a float64). {{- define "zkservers" -}} {{- $zkservers := list -}} {{- range int . | until -}} {{- $zkservers := print "zk-" . ".zookeeper" | append $zkservers -}} {{- end -}} {{- join "," $zkservers -}} {{- end -}} For an input of, say, 3 I'm expecting this to produce: zk-0.zookeeper,zk-1.zookeeper,zk-2.zookeeper It produces nothing. I understand that the line within the range block is a no-op since the variable $zkservers is a new variable

I have an umbrella chart with multiple sub-charts, I simply want to make sure that subchart1 runs before subchart2, etc. How can we define the order of subchart execution? Seems like hook-weights only apply relative to the chart that declares them. VAS Here is a part of the Helm documentation related to execution order of charts: The above sections explain how to specify chart dependencies, but how does this affect chart installation using helm install and helm upgrade? Suppose that a chart named "A" creates the following Kubernetes objects namespace "A-Namespace" statefulset "A-StatefulSet"

Helm charts define helper templates in _helpers.tpl which are used to create normalized names for the services. The standard form of the template for a service (DNS) name is: {{- define "postgresql.fullname" -}} {{- $name := default .Chart.Name .Values.nameOverride -}} {{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" -}} {{- end -}} If using postgresql as a subchart, how are you supposed to use DNS-based service discovery to refer to it? A common pattern seems to be to copy the subchart helpers into the parent chart. {{- define "keycloak.postgresql.fullname" -}} {{- $name :=