kubernetes-helm

问题 getting this error from today evening in google cloud . Something happened wrong with gcloud. Same commands were working till yesterday. helm install --name nginx-ingress stable/nginx-ingress --set rbac.create=true --set controller.publishService.enabled=true i have followed steps: https://cloud.google.com/community/tutorials/nginx-ingress-gke enter image description here (mykubeproject1)$ helm install --name nginx-ingress stable/nginx-ingress --set rbac.create=true --set controller

问题 I am using Airflow with Kubernetes executor and testing out locally (using minikube), While I was able to get it up and running, I cant seem to store my logs in S3. I have tried all solutions that are described and I am still getting the following error, *** Log file does not exist: /usr/local/airflow/logs/example_python_operator/print_the_context/2020-03-30T16:02:41.521194+00:00/1.log *** Fetching from: http://examplepythonoperatorprintthecontext-5b01d602e9d2482193d933e7d2:8793/log/example

问题 I'm having trouble understanding helm 's use of helm --kube-context=microk8s install ... should install into the context microk8s thus into my local microk8s cluster rather than the remote GKE cluster which I once connected to. This however fails due to Error: could not get Kubernetes config for context "microk8s": context "microk8s" does not exist if I run e.g. helm --kube-context=microk8s install --name mereet-kafka after successfully running helm init and adding necessary repositories. The

问题 With Helm v3.0.2 + a new Kubernetes v1.14.9 cluster. fyi, I've already added the stable repo: helm repo add stable https://kubernetes-charts.storage.googleapis.com/ helm install \ --namespace prometheus \ prom-dry-run \ stable/prometheus-operator \ --dry-run manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info:

问题 Is it possible to directly modify the file mounted by configMap ? We have an application that reads a configuration file that was configMap type and the application should able to edit the file and the changes should be persisted if the configMap is shared with other pods and when the pod restarts. If configMap is not meant for this, then what should we relay on consul to save the configuration? 回答1: Yes a configmap is not intended to be writeable. If you're interacting with files from a

问题 I have a kind: Namespace template yaml like follows, apiVersion: v1 kind: Namespace metadata: name: {{ .Values.namespace }} namespace: "" How do I make helm install create the above-given namespace ( {{ .Values.namespace }} ) if and only if above namespace ( {{ .Values.namespace }} ) doesn't exits in the pointed kubernets cluster 回答1: For helm2 it's best to avoiding creating the namespace as part of your chart content if at all possible and letting helm manage it. helm install with the -

问题 I want to perform a helm upgrade on a GKE k8s cluster. I am executing the following command helm upgrade --force --tls --install --set master.installPlugins=[u'kubernetes:1.21.2', u'workflow-job:2.36', u'workflow-aggregator:2.6', u'credentials-binding:1.20', u'git:4.0.0'] --set master.tag=lts --set agent.tag=3.27-1 -f /org_files/tmp/kerkyra-jenkins/jenkins-values.yaml --namespace jenkins my-jenkins stable/jenkins However it fails with the following name: Error: This command needs 2 arguments:

问题 I have created helm chart for varnish cache server which is running in kubernetes cluster , while testing with the "external IP" generated its throwing error , sharing below Sharing varnish.vcl, values.yaml and deployment.yaml below . Any suggestions how to resolve as I have hardcoded the backend/web server as .host="www.varnish-cache.org" with port : "80". My requirement is on executing curl -IL I should get the response with cached values not as described above (directly from backend server

问题 I use an install script in a post-install hook. When I run helm install with --wait option, helm waits that all pods are ready, but helm does not launch post-install hooks script. Then, the pods are not yet ready (pods are waiting for install script to finish). I tried with pre-install hook instead, but the install script needs other services to be running... PS: it works fine if I don't use "--wait", but CI from gitlab won't fail if there is an error during pod startups. Is there a way to

问题 Use https://docs.gitlab.com/ce/install/kubernetes/gitlab_omnibus.html#configuring-and-installing-gitlab for install GitLab. But I have a problem. I see in describe gitlab pod: Warning Unhealthy 1m (x195 over 39m) kubelet, k8s-m3.me Readiness probe failed: Get http://10.233.105.52:8005/health_check?token=SXBAQichEJasbtDSygrD: dial tcp 10.233.105.52:8005: getsockopt: connection refused Kubernetes v1.10.2 # kubectl get pods -owide NAME READY STATUS RESTARTS AGE IP NODE gitlab1-gitlab-75576c4589