Hot answers tagged

3

I believe this is an current bug in k3s that upstream DNS is hardcoded to 1.1.1.1. this should be resolved shortly https://github.com/rancher/k3s/issues/53


2

ibuildthecloud9 gave me the right hint. Since the github issue doesn't describe how to midify the dns, I figured it out and want to document it here in case someone need to change it, too. It's stored in the configmap coredns as Corefile: proxy . 1.1.1.1 You need to replace this by your dns server (192.168.0.19 in my case). It could be done manually using ...


2

Yes this happens frequently when debugging helm releases. The problem happens when a previously failed release is preventing you from updating it. If you run helm ls you should see a release in state FAILED. You might have deleted it in which case it might show up with helm ls -a. Such a release cannot be upgraded using the normal approach of having helm ...


1

This can happen with releases in FAILED state as mentioned by simbo1905 in her/his answer. Another case is if there's a previously deleted but not purged release with the same name. Doing another delete with the purge option on the release will free the name for reuse. helm ls -a helm ls -a | grep -e NAME -e name_of_release helm delete --purge ...


1

You need to add the jenkins user to the docker group: # run the following command as root usermod -aG docker jenkins


1

I've eventually created an umbrella chart with alias: dependencies: - name: app repository: file://./app version: 1.0.0 alias: child1 - name: app repository: file://./app version: 1.0.0 alias: child2 And in values.yaml i've changed the needed values, then added the grafana dashboard in the bundled yaml file.


1

See my answer here: Ran into this today when trying to use Garden.io for a cluster running in Jelastic. Found the solution in this Github comment: First acquire a local binary for Tiller (server-version of Helm), either by compiling or by downloading it from the release page. Then run: $ export HELM_HOST=":44134" $ tiller -listen ${...


1

A co-worker ended up taking over deploying this a few days ago and managed to get it working. I'm not certain what he did differently, but I know discovered very similar issues I was facing with other Helm charts boiled down to the database they depended on not deploying properly which caused the other components to fail during initialization. Database ...


1

I learned that it's not required to set the ingress class to nginx as I did in kubernetes.io/ingress.class: nginx. All annotations prefixed with nginx.ingress.kubernetes.io apply to the default Kubernetes ingress. Setting the timeouts is also not required. The only important annotation is nginx.ingress.kubernetes.io/proxy-body-size: "0" because the default ...


1

Check https://github.com/helm/helm/issues/3130, this might help. I followed the instruction in the post: kubectl --namespace kube-system create serviceaccount tiller kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller helm init --service-account tiller --upgrade This works for me.


1

Finnaly, I found the solution, thanks to @simbo1905. All that I need to fix that problem: values.yaml Child Chart 1 (or two) postgresql: nameOverride: chart-1-postgres In the Child Chart 2 nameOverride became to chart-2-postgres.


1

How I see there is two options (from my exp): Use configuration for provider. https://www.terraform.io/docs/providers/helm/index.html, there is option to install tiller. Use prefabricated modules, for example: https://github.com/sagikazarmark/terraform-tiller https://registry.terraform.io/modules/Vidimensional/tiller/kubernetes/0.0.1


1

Checkout flux(https://github.com/weaveworks/flux/), it introduces a new kubernetes crd called HelmRelease, in which you can include your helm release info(like the chart repo, name, version, namespace, and values. You can even pull your charts from a git repo). The flux controller monitors a git repo of your choice(you can monitor a path inside the repo as ...


1

My 2 cents. We have similar requirement like you do. We end up having multiple values files in the form of values-<namespace>.yaml and it should come with the defaults set to values.yaml We also have some shell scripts to deploy to the namespace. Something like this deploy.sh --namespace app. It is not without its problem, the number of files are ...


1

Usually to access an external API you can just use its URL. But you can create a Service for it if you like, the type of service should be ExternalName as described in the documentation https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types


1

A service in kubernetes is (mostly) used for internal communication. If you want to access an external resource by domain/ip you can just do so. If you have an IP address and you would like to have some sort of domain connected to it, you could you am service with the external name field set to the up address (we use that for database purposes). An endpoint ...


1

you can use terraform to install helm charts, you dont have to obviously something is probably wrong with your kubernetes connection, check if its actually working


Only top voted, non community-wiki answers of a minimum length are eligible