This message was deleted.
# epinio
a
This message was deleted.
b
Hi Antonio, as Fred said these Epinio services are more just for testing, but they can still be used. Since you have found many "issues" it's probably better trying to explain it one by one! keep in mind that the provided services are just deploying "standard" Bitnami services, and all the values are the default! Regarding the internal route it's the one shown in the
epinio service show
command, so it's the
x33d3de604f8682ca102ee497ffaf-postgresql.mynamespace.svc.cluster.local:5432
. Since the app is running in the same namespace you can actually just use
x33d3de604f8682ca102ee497ffaf-postgresql:5432
if you want. 🙂 For the
<http://servicebinding.io/postgresql|servicebinding.io/postgresql>
it's an interesting catch. From a quick look it should be fetched, so maybe it's a bug. If you want to file an issue for this specific case, maybe with an example, we will have a look at it. Otherwise I will do it.
from the last Epinio version (1.9.0) we have added the support for the user to customize some values for their specific service (with the
--chart-value
option, see), and also you could fetch some info about the service chart from some metadata and customize your releses, with something like
"{{ .Values.epinio.serviceName }}"
(see). So with some tweaks now you should be able to do almost "whatever" you want.