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 ...
Finnaly, I found the solution, thanks to @simbo1905.
All that I need to fix that problem:
values.yaml Child Chart 1 (or two)
In the Child Chart 2 nameOverride became to chart-2-postgres.
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 ...
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 ...
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
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 ...
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 . 220.127.116.11
You need to replace this by your dns server (192.168.0.19 in my case). It could be done manually using ...
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 ...
Use a docker image within your pipeline that has helm and other tools installed.
To quote the docs:
Pipeline is designed to easily use Docker images as the execution
environment for a single Stage or the entire Pipeline. Meaning that a
user can define the tools required for their Pipeline, without having
to manually configure agents. Practically ...
I ended up using stolon for its automatic leader election and fail over handling.
Crunchy Data offers small building blocks so there is a lot of work to do to put them all together while stolon has a ready helm chart.
But I didn't try patroni since stolon worked just fine.