kubernetes-helm

Tiller is not working properly in my kubernetes cluster. I want to delete everything Tiller. Tiller (2.5.1) has 1 Deployment, 1 ReplicaSet and 1 Pod. I tried: kubectl delete deployment tiller-deploy -n kube-system results in "deployment "tiller-deploy" deleted" however, tiller-deploy is immediately recreated kubectl get deployments -n kube-system shows tiller-deploy running again I also tried: kubectl delete rs tiller-deploy-393110584 -n kube-system results in "replicaset "tiller-deploy-2745651589" deleted" however, tiller-deploy-2745651589 is immediately recreated kubectl get rs -n kube

I have my deployment.yaml file within the templates directory of Helm charts with several environment variables for the container I will be running using Helm. Now I want to be able to pull the environment variables locally from whatever machine the helm is ran so I can hide the secrets that way. How do I pass this in and have helm grab the environment variables locally when I use Helm to run the application? Here is some part of my deployment.yaml file ... ... spec: restartPolicy: Always containers: - name: sample-app image: "sample-app:latest" imagePullPolicy: Always env: - name: "USERNAME"

I am getting a couple of errors with Helm that I can not find explanations for elsewhere. The two errors are below. Error: no available release name found Error: the server does not allow access to the requested resource (get configmaps) Further details of the two errors are in the code block further below. I have installed a Kubernetes cluster on Ubuntu 16.04. I have a Master (K8SMST01) and two nodes (K8SN01 & K8SN02). This was created using kubeadm using Weave network for 1.6+. Everything seems to run perfectly well as far as Deployments, Services, Pods, etc... DNS seems to work fine,

I have installed helm 2.6.2 on the kubernetes 8 cluster. helm init worked fine. but when I run helm list it giving this error. helm list Error: configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list configmaps in the namespace "kube-system" How to fix this RABC error message? sfgroups Once these commands: kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":

I have minikube and kubectl installed: $ minikube version minikube version: v1.4.0 commit: 7969c25a98a018b94ea87d949350f3271e9d64b6 $ kubectl version Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9",

I, based on the sample below, created both webfrontend and mywebapi, https://docs.microsoft.com/en-us/azure/dev-spaces/get-started-netcore-visualstudio and based on the charts folder below from this example, I created similar charts folder for the example above. https://docs.microsoft.com/en-us/azure/dev-spaces/quickstart-team-development https://github.com/Azure/dev-spaces/tree/master/samples/BikeSharingApp/charts However, I got errors below when running the script below: The whole project is available from https://github.com/PingPongSet/AzureDevSpaces az group create --name MyResourceGroup -

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 . Update 2: Helm 3 added support for multi namespaces https://github.com/helm/helm/issues/2060 Update 1: If a resource template specifies a metadata.namespace , then it will be installed