kubernetes-helm

问题 I am deploying jupyterhub on a kubernetes cluster. In the config.yaml file, I am specifying a registry and the image tag. While 3 pods are successfully created, one is not. I could not find much content pertaining to jupyter-hub. The helm chart can be found here(https://jupyterhub.github.io/helm-chart/jupyterhub-0.8.2.tgz). My config for values.yaml is: proxy: secretToken: "some token" singleuser: image: name: acc_id.dkr.ecr.ap-south-1.amazonaws.com/demo tag: 12c lifecycleHooks: postStart:

问题 I have Keycloak behind Kong Ingress Controller. I 'm able to see keycloak welcome page at my {url}/auth/. However, when I click at Administration Console I am redirected to {url}:8443/auth/admin/master/console/ When I click at Administration Console I should be redirect to {url}/auth/admin/master/console/ When I install keycloak (with helm) on minikube exposing the the service as a NodePort service without using ingress and load balancer I'm able to access Administration Console page. I have

问题 I have a Kubernetes cluster that runs a number of independent, discrete services. I want to use helm to deploy them, and I have made a helm chart for every individual resource. However, now I want to be able to deploy the cluster as a single entity, but it is not clear to me how helm supports stitching together multiple charts. When I look at example repos, they simply have every single template file in the template folder of a single chart, and then a giant, sprawling Values.yaml file. To me

问题 I followed Istio's official documentation to setup Istio for sample bookinfo app with minikube. but I'm getting Unable to connect to the server: net/http: TLS handshake timeout error. these are the steps that I have followed(I have kubectl & minikube installed). minikube start curl -L https://git.io/getLatestIstio | sh - cd istio-1.0.3 export PATH=$PWD/bin:$PATH kubectl apply -f install/kubernetes/helm/istio/templates/crds.yaml kubectl apply -f install/kubernetes/istio-demo-auth.yaml kubectl

问题 Is there a way to conditionally install a helm subchart based on global values.yaml? I've all my internal services and components as subcharts, and one of them is a messagequeue chart. In my dev and test environment (local k8s), I use RabbitMQ, and in staging and Prod (AKS), I use Azure Service Bus. Based on the namespace/values.yaml, I want to install rabbitmq or not. P.S - I've created all the components as subcharts so that they are all part of a single release. 回答1: I've found out the

问题 The plan is to move my dockerized application to Kubernetes. The docker container uses couple of files - which I used to mount on the docker volumes by specifying in the docker-compose file: volumes: - ./license.dat:/etc/sys0/license.dat - ./config.json:/etc/sys0/config.json The config file would be different for different environments, and the license file would be the same across. How do I define this in a helm template file (yaml) so that it is available for the running application? What

问题 When I try to install a chart with helm: helm install stable/nginx-ingress --name my-nginx I get the error: Error: unknown flag: --name But I see the above command format in many documentations. Version: version.BuildInfo{Version:"v3.0.0-beta.3", GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a", GitTreeState:"clean", GoVersion:"go1.12.9"} Platform: Windows 10 64 What could be the reason? 回答1: In Helm v3, the release name is now mandatory as part of the commmand, see helm install --help :

问题 I'm setting up ELK services in Azure Kubernetes Service. But I only see this error: "Kibana server is not ready yet" I'm using Helm to install the stable/elastic-stack release without any changes (default for everything) in AKS. helm install --name elk stable/elastic-stack And I also added an ingress controller to expose the Kibana server to public. However, I only see "Kibana server is not ready yet" error. I've checked the Kibana pod is running, as well as the ElasticSearch. As a newbie in

问题 Ultimately i'm trying to get an array of strings e.g. ['foo', 'bar'] in my js app from my helm config. ./vars/dev/organizations.yaml ... organizations: - 'foo' - 'bar' ... ./templates/configmap.yaml ... data: organizations.yaml: | organizations: "{{ toYaml .Values.organizations | indent 4 }}" ... ./templates/deployment.yaml ... containers: args: - "--organizations-config" - "/etc/app/cfg/organizations.yaml" ... index.js ... const DEFAULT_ORGANIZATIONS_PATH = './vars/local/organizations.yaml'

问题 I am using helm charts to deploy pods with a "ConfigMap" managing the configurations. I edit ConfigMap directly to make changes to configuration files and then delete pods using kubectl delete, for the new configuration to take effect. Is there any easy way using helm to replace a running pod with the new configuration without executing " kubectl delete " command 回答1: We have found that using --recreate-pods will immediately terminate all running pods of that deployment, meaning some downtime