kubernetes-helm

问题 I want to run different test suites on my helm release in different (partly manual) CI jobs. How do I best execute these test suites from a CI job? Details: With a single test suite, helm test is very helpful. But how can I easily tell helm test which test suite to execute? Currently, I have only two test suites A and B and an environment variable SUITE I inject via helm install. The test job decides based on the value of SUITE which test suite to execute. But this injection is complex and I

问题 Is it possible to do the following,(and has anyone been successful) Having 2 jobs as separate files: helm/tree/master/general/templates/tests/job1.yaml helm/tree/master/general/templates/tests/job2.yaml Call either file using e.g. helm test general/job1.yaml -n ENV Instead of helm test general -n ENV Or is it limited to all files in that folder being run sequentially? 来源： https://stackoverflow.com/questions/60818255/can-helm-test-be-used-to-run-separate-suites

问题 I am installing a helm chart which has a ingress.yaml template. I get this error: Error: render error in "chartmuseum/templates/ingress.yaml": template: chartmuseum/templates/ingress.yaml:35:22: executing "chartmuseum/templates/ingress.yaml" at <.Values.service.servicename>: nil pointer evaluating interface {}.service I am not able to find where the problem is. The same set of if else structure works abolutely fine in the service.yaml of the same helm chart. - path: {{ default "/" .path |

问题 I am installing a helm chart which has a ingress.yaml template. I get this error: Error: render error in "chartmuseum/templates/ingress.yaml": template: chartmuseum/templates/ingress.yaml:35:22: executing "chartmuseum/templates/ingress.yaml" at <.Values.service.servicename>: nil pointer evaluating interface {}.service I am not able to find where the problem is. The same set of if else structure works abolutely fine in the service.yaml of the same helm chart. - path: {{ default "/" .path |

问题 I am currently writing a Helm chart for a multi-container application. We have a bunch of microservice containers (we call them "applications") that are very similar in the way they can be handled through K8s, and can (and thus should) be handled by the same Helm template to avoid duplicating things. On the other hand, it makes sense to be able to configure certain settings individually for the different applications (e.g., resource requests). I am currently doing something like this: {{-

问题 I am trying to delete/remove all the pods running in my environment. When I issue docker ps I get the below output. This is a sample screenshot. As you can see that they are all K8s. I would like to delete all of the pods/remove them. I tried all the below approaches but they keep appearing again and again sudo kubectl delete --all pods --namespace=default/kube-public #returns "no resources found" for both default and kube-public namespaces sudo kubectl delete --all pods --namespace=kube

问题 I am trying to delete/remove all the pods running in my environment. When I issue docker ps I get the below output. This is a sample screenshot. As you can see that they are all K8s. I would like to delete all of the pods/remove them. I tried all the below approaches but they keep appearing again and again sudo kubectl delete --all pods --namespace=default/kube-public #returns "no resources found" for both default and kube-public namespaces sudo kubectl delete --all pods --namespace=kube

问题 I am trying to delete/remove all the pods running in my environment. When I issue docker ps I get the below output. This is a sample screenshot. As you can see that they are all K8s. I would like to delete all of the pods/remove them. I tried all the below approaches but they keep appearing again and again sudo kubectl delete --all pods --namespace=default/kube-public #returns "no resources found" for both default and kube-public namespaces sudo kubectl delete --all pods --namespace=kube

问题 I'm playing around wiht minikube and I have a config in my values.yaml defined like this image: repository: mydocker.jfrog.io/mysql I want it to point a to a local docker image that lives locally mysql/docker/dockerfile I'm not sure what the syntax is can't find it in the docs 回答1: Check the list of images on your local machine with docker image ls . Let’s say rajesh12/mysql is the image you want to use: image: repository: rajesh12/mysql 回答2: This is a late reply. But I solved it by this way.

问题 I am trying to run Sonarqube service using the following helm chart. So the set-up is like it starts a MySQL and Sonarqube service in the minikube cluster and Sonarqube service talks to the MySQL service to dump the data. When I do helm install followed by kubectl get pods I see the MySQL pod status as running , but the Sonarqube pos status shows as CreateContainerConfigError . I reckon it has to do with the mounting volume thingy: link. Although I am not quite sure how to fix it (pretty nnew